From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: Rik van Riel <riel@nl.linux.org>,
Kanoj Sarcar <kanoj@google.engr.sgi.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.rutgers.edu,
linux-mm@kvack.org
Subject: Re: Getting big areas of memory, in 2.3.x?
Date: Thu, 9 Dec 1999 18:09:24 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.991209180518.21542B-100000@kanga.kvack.org> (raw)
In-Reply-To: <Pine.LNX.4.10.9912100015520.10946-100000@chiara.csoma.elte.hu>
On Fri, 10 Dec 1999, Ingo Molnar wrote:
> On Thu, 9 Dec 1999, Rik van Riel wrote:
>
> > a "real" zoned allocator. Not a 2.4 thing,
>
> would you mind elaborating what such a "real" zoned allocator has,
> compared to the current one?
The type of allocation determines what pool memory is allocated from. Ie
nonpagable kernel allocations come from one zone, atomic allocations from
another and user from yet another. It's basically the same thing that the
slab does, except for pages. The key advantage is that allocations of
different types are not mixed, so the lifetime of allocations in the same
zone tends to be similar and fragmentation tends to be lower.
-ben
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-12-09 23:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 1:03 Jeff Garzik
1999-12-09 2:28 ` Alan Cox
1999-12-09 2:45 ` Jeff Garzik
1999-12-09 5:22 ` Oliver Xymoron
1999-12-09 12:25 ` Ingo Molnar
1999-12-09 20:24 ` Jeff Garzik
1999-12-09 20:31 ` Kanoj Sarcar
1999-12-09 20:39 ` Rik van Riel
1999-12-09 20:54 ` Kanoj Sarcar
1999-12-09 23:21 ` Ingo Molnar
1999-12-09 22:27 ` Kanoj Sarcar
1999-12-09 23:16 ` Ingo Molnar
1999-12-09 23:09 ` Benjamin C.R. LaHaise [this message]
1999-12-10 0:44 ` Ingo Molnar
1999-12-10 0:18 ` William J. Earl
1999-12-11 19:56 ` Stephen C. Tweedie
1999-12-10 12:21 ` Rik van Riel
1999-12-10 13:42 ` Ingo Molnar
1999-12-10 18:04 ` William J. Earl
1999-12-09 20:50 ` William J. Earl
1999-12-09 23:15 ` Ingo Molnar
1999-12-09 22:13 ` William J. Earl
1999-12-09 22:26 ` Alan Cox
1999-12-09 23:42 ` William J. Earl
1999-12-09 23:50 ` Alan Cox
1999-12-10 0:30 ` William J. Earl
1999-12-10 0:37 ` Alan Cox
1999-12-10 4:19 ` Oliver Xymoron
1999-12-10 10:14 ` Thomas Sailer
1999-12-09 23:24 ` Ingo Molnar
1999-12-09 22:33 ` Jeff Garzik
1999-12-09 23:32 ` Rogier Wolff
1999-12-09 23:44 ` JF Martinez
1999-12-10 0:52 ` Ingo Molnar
1999-12-09 23:46 ` Andi Kleen
1999-12-10 13:52 ` Stephen C. Tweedie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.96.991209180518.21542B-100000@kanga.kvack.org \
--to=blah@kvack.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=kanoj@google.engr.sgi.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--cc=riel@nl.linux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox