Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Oct 2000 11:27:50 -0800
From:      David Greenman <dg@root.com>
To:        Bosko Milekic <bmilekic@dsuper.net>
Cc:        freebsd-net@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG
Subject:   Re: MP: per-CPU mbuf allocation lists 
Message-ID:  <200010301927.LAA01623@implode.root.com>
In-Reply-To: Your message of "Mon, 30 Oct 2000 13:20:52 EST." <Pine.BSF.4.21.0010301256580.30271-100000@jehovah.technokratis.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
>  	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?

-DG

David Greenman
Co-founder, The FreeBSD Project - http://www.freebsd.org
President, TeraSolutions, Inc. - http://www.terasolutions.com
Pave the road of life with opportunities.


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?200010301927.LAA01623>