Re: HEADSUP: MPSAFE network drivers

From: Pawel Jakub Dawidek (nick_at_garage.freebsd.pl)
Date: 10/30/03

  • Next message: Richard Nyberg: "Re: problems with sysinstall" 
    Date: Thu, 30 Oct 2003 10:22:38 +0100
To: Sam Leffler <sam@errno.com>

    On Wed, Oct 29, 2003 at 11:52:48AM -0700, Sam Leffler wrote:
    +> I'm committing changes to mark various network drivers' interrupt handlers
    +> MPSAFE. To insure folks have a way to backout if they hit problems I've also
    +> added a tunable that lets you disable this w/o rebuilding your kernel. By
    +> default all network drivers that register an interrupt handler INTR_MPSAFE
    +> are setup to run their ISR w/o Giant. If you want to defeat this w/o
    +> changing the code you can set
    +>
    +> debug.mpsafenet=0
    +>
    +> from the loader when booting and the MPSAFE bit will automatically be removed.
    +> I plan to use this to also control forthcoming changes for registering MPSAFE
    +> netisrs.
    +>
    +> The following drivers are marked MPSAFE:
    +>
    +> ath, em, ep, fxp, sn, wi, sis
    +>
    +> I've got changes coming for bge. Other drivers probably can be marked MPSAFE
    +> but I'm only doing it for those drivers that I can test.

    Because there is so many drivers, maybe you could prepare some regression
    tests designed to check changed things. This will allow people to test your
    changes - it is not very easy now if we don't know what we're looking for
    exactly PLUS those drivers aren't marked MPSAFE by default. 

    -- 
Pawel Jakub Dawidek                       pawel@dawidek.net
UNIX Systems Programmer/Administrator     http://garage.freebsd.pl
Am I Evil? Yes, I Am!                     http://cerber.sourceforge.net

  • Next message: Richard Nyberg: "Re: problems with sysinstall"

    Relevant Pages

    • HEADSUP: MPSAFE network drivers
      ... I'm committing changes to mark various network drivers' interrupt handlers ... are setup to run their ISR w/o Giant. ... from the loader when booting and the MPSAFE bit will automatically be removed. ...
      (freebsd-current)
    • Re: HEAD UP: non-MPSAFE network drivers to be disabled (was: 8.0 network stack MPsafety goals (f
      ... > of the general problem and list of specific drivers below. ... > non-MPSAFE network device drivers. ... > device driver, take action to make sure it doesn't remain on ... One of these is the USB-based drivers, which require an MPSAFE USB stack ...
      (freebsd-questions)
    • Re: Reminder: non-mpsafetty drivers to be connected on Sunday
      ... Comments on the patch are very welcome! ... This patch just disconnects the majority of the serial drivers from ... A MPSAFE tty subsystem is infinitely more important than any particular ... we didn't throw out half the NIC drivers when we did the ...
      (freebsd-arch)
    • Re: Reminder: non-mpsafetty drivers to be connected on Sunday
      ... Comments on the patch are very welcome! ... This patch just disconnects the majority of the serial drivers from ... A MPSAFE tty subsystem is infinitely more important than any particular ... we didn't throw out half the NIC drivers when we did the ...
      (freebsd-current)
    • Re: OSD - Image size... your thoughts?
      ... The main reason I've left network drivers ... in the image because it won't download the network drivers during post ... With OSD you can also use download and execute scenarios ... and take use of SMS Client caching techniques to preload the wim-file ...
      (microsoft.public.sms.tools)