Re: HEADS UP: network locking work going on

From: Scott Long (scottl_at_freebsd.org)
Date: 08/20/03

  • Next message: Sam Leffler: "Re: HEADS UP: network locking work going on" 
    Date: Tue, 19 Aug 2003 20:11:56 -0600
To: Sam Leffler <sam@errno.com>

    Sam Leffler wrote:
    > I'm actively working on improving the network performance of -current.
    > Much of this work involves removing Giant from the network stack. I've
    > already been in touch with many developers that are working in this
    > area; this note is to insure "everyone" is aware. If your are actively
    > working on stuff related to the network code and I haven't already
    > corresponded with you; please let me know so we can coordinate our
    > work--I have no interest in duplicating the efforts of others.
    > Otherwise, if you are working in this area I'd appreciate knowing about
    > any significant changes planned that might affect what I'm doing.
    >
    > As to the work itself, the overall goal is to bring the performance for
    > "normal network use" back to at least that of -stable. This is to be
    > done in time for the 5.2 release though the specifics of what is
    > included in 5.2 are to be determined. Obviously the main work here is
    > to remove Giant and to that end I've already made a pass over the
    > following areas (in no specific order):
    >
    > raw sockets
    > routing table (except multicast routing)
    > fast ipsec
    > fast forwarding
    > bridge
    > ipfw
    > 802.11 layer
    > fxp, em, sis, wi, and ath drivers
    >

    Excellent!

    Is there any consideration for running some hardware drivers with Giant
    while they are converted?

    Scott

    _______________________________________________
    freebsd-arch@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-arch
    To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"

  • Next message: Sam Leffler: "Re: HEADS UP: network locking work going on"

    Relevant Pages

    • Re: Running the network stack without Giant -- change in default coming
      ... > to allow the network stack to run in parallel on multiple processors ... > currently unsafe without the Giant lock turned on. ... > configuration for testing out the impact of disabling Giant on MP ...
      (freebsd-current)
    • Running the network stack without Giant -- what to try and when
      ... As many of you have seen from status reports, e-mails, bug reports, etc, ... the FreeBSD Project has been working for some time on getting the network ... without the Giant lock, and we're ready for more people to start running ... - While we've been doing pretty heavy testing in MPSAFE configurations, ...
      (freebsd-current)
    • Removing NET_NEEDS_GIANT: first patch
      ... This source code declaration was used by optionally compiled components to declare a strict requirement for Giant, and forced Giant over the entire network stack. ... retrieving revision 1.13 ... diff -u -r1.13 amrr.c ...
      (freebsd-current)
    • Removing NET_NEEDS_GIANT: first patch
      ... This source code declaration was used by optionally compiled components to declare a strict requirement for Giant, and forced Giant over the entire network stack. ... retrieving revision 1.13 ... diff -u -r1.13 amrr.c ...
      (freebsd-arch)
    • Re: HEADS UP: IPX over IP support removed
      ... The use of Giant for interfaces has caused some complication in getting the locking right during my passes over the Layer 2 network code and IPv4 code. ... Hopefully in 8.0 we will be able to drop support for non-MPSAFE network device drivers. ... I believe it is reasonable to call time on netatm, though I haven't heard recently from the guy I donated hardware to in order to work on this. ...
      (freebsd-current)