Date: Mon, 30 Oct 2000 14:14:03 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: David Greenman <dg@root.com> Cc: Bosko Milekic <bmilekic@dsuper.net>, freebsd-net@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Subject: Re: MP: per-CPU mbuf allocation lists Message-ID: <Pine.BSF.4.21.0010301412440.32006-100000@beppo.feral.com> In-Reply-To: <200010301927.LAA01623@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Oct 2000, David Greenman wrote: > > I recently wrote an initial "scratch pad" design for per-CPU mbuf > > lists (in the MP case). The design consists simply of introducing > > these "fast" lists for each CPU and populating them with mbufs on bootup. > > Allocations from these lists would not need to be protected with a mutex > > as each CPU has its own. The general mmbfree list remains, and remains > > protected with a mutex, in case the per-CPU list is empty. > > I have only one question - is the lock overhead really so high that this > is needed? If you know that you can also pre-busdma wrap these lists (which is required for full alpha support, and may(?) be for ia64), yes, this makes sense to me (at least). I had a friend at Sun not speak to me for years because I didn't do this for the Solaris DKI/DDI. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010301412440.32006-100000>