Date: Wed, 27 Feb 2002 12:51:11 -0800 From: Terry Lambert <tlambert2@mindspring.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Alfred Perlstein <bright@mu.org>, Julian Elischer <julian@elischer.org>, Jeff Roberson <jroberson@chesapeake.net>, arch@FreeBSD.ORG Subject: Re: Slab allocator Message-ID: <3C7D46BF.CE88CDEA@mindspring.com> References: <200202271926.g1RJQCm29905@apollo.backplane.com> <Pine.BSF.4.21.0202271128580.97278-100000@InterJet.elischer.org> <20020227194256.GR80761@elvis.mu.org> <200202271955.g1RJtAj30178@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon wrote: > :It's basically the pre-emption stuff you guys are wondering about > :along with the possiblity of free'ing back to another cpu's > :cache that may be an issue. > : > :Jeff, are you fee'ing memory back to the cache it was initially > :allocated from or not? > > I don't know what Jeff is doing there but I do seem to recall a > paper from somewhere that indicated it was more efficient to free memory > to the current cpu's per-cpu cache rather then back to the original > cpu's cache because the current cpu's hardware L1/L2 cache likely already > has mastership of the memory. I think Linux does things this way. I think you are thinking of: Experience With an Efficient Parallel Kernel Memory Allocator Paul E. McKenney Jack Slingwine Phil Krueger Sequent Computer Systems, Inc. The paper is available at: http://citeseer.nj.nec.com/484408.html They used a "second chance" three layer coelescing strategy, where a third level coelesced freed objects back into pages for return to the host OS. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C7D46BF.CE88CDEA>