ru.unix.bsd

 
 - RU.UNIX.BSD ------------------------------------------------------------------
 From : Slawa Olhovchenkov                   2:5030/500     07 Oct 2007  18:21:36
 To : All
 Subject : Вести с полей
 -------------------------------------------------------------------------------- 
 

 
 From: Robert Watson <rwatson@FreeBSD.org>
 Subject: HEADS UP: debug.mpsafenet removed
 
 This is the first of two e-mails relating to the removal of
 Giant-compatibility code from the network protocol stack.  Please read both.
 
 Per intermittent e-mails and notifications over the last three years, I have
 now removed the NET_NEEDS_GIANT() and debug.mpsafenet machinery from the
 7-CURRENT kernel.  This is, in principle, largely a no-op, as no
 NET_NEEDS_GIANT() components remain in the kernel, and all remaining
 components are intended to be MPSAFE, and the vast majority of users have
 been running without Giant over the network stack since about FreeBSD 5.3.
 However, bumps inevitably happen, so please let me know:
 
 - *If* you are using credential-based rules in your ipfw or pf firewall
   configuration, this may trigger WITNESS lock order reversal warnings.  We
   plan to suppress these warnings before the release, so the warnings alone
   should not present a problem.  However, if you experience deadlocks as a
   result, drop e-mail to current@ as soon as possible so that they can be
   diagnosed and fixed.
 
 - *If* you have been running with debug.mpsafenet because it suppressed some
   other warning you have, to date, neglected to e-mail current@ about, or not
   reminded us about frequently, *and* it now recurs as a result of
   debug.mpsafenet going away, please send e-mail to current@ as soon as
   possible.
 
 A series of follow-up commits to remove various straggling references and
 compatibility pieces will now occur, including converting all
 NET_CALLOUT_MPSAFE references to CALLOUT_MPSAFE, and removing calls to
 NET_*_GIANT() at various points in the protocol and driver code.
 
 Non-MPSAFE device drivers flagged with IFF_NEEDSGIANT should remain
 unaffected, as the code to acquire Giant before entering from the network
 stack will remain in place, and those drivers will not be passing the MPSAFE
 flag into the interrupt registration code.
 
 Thanks,
 
 Robert N M Watson
 Computer Laboratory
 University of Cambridge
 ... Hовые сапоги всегда жмут.
 --- GoldED+/BSD 1.1.5
  * Origin:  (2:5030/500)
 
 

Вернуться к списку тем, сортированных по: возрастание даты  уменьшение даты  тема  автор