HEADS UP: network locking work going on

[Scott Long]

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