Date: Tue, 1 Aug 2006 08:30:33 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Robert Watson <rwatson@FreeBSD.org> Cc: arch@FreeBSD.org, net@FreeBSD.org Subject: Re: Changes in the network interface queueing handoff model Message-ID: <17615.18793.700752.342809@grasshopper.cs.duke.edu> In-Reply-To: <20060730141642.D16341@fledge.watson.org> References: <20060730141642.D16341@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson writes: > > 5BOne of the ideas that I, Scott Long, and a few others have been bouncing > around for some time is a restructuring of the network interface packet > transmission API to reduce the number of locking operations and allow network > device drivers increased control of the queueing behavior. Right now, it <....> > - The ifnet send queue is a separately locked object from the device driver, > meaning that for a single enqueue/dequeue pair, we pay an extra four lock > operations (two for insert, two for remove) per packet. > Going forward, especially now that we support sun4v CoolThreads hardware, we're going to want to rethink the "single lock" per transmit routine model that most drivers have. The most expensive operation in transmit routines is bus_dmamap_load_mbuf_sg(), especially when there is an IOMMU involved (like on CoolThreads machines) and there is no reason why this needs to be called with a driver's transmit lock held. I have hard data (from Solaris) about how much fine grained locking in a 10GbE driver's transmit routine helps. Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17615.18793.700752.342809>