From: Hirokazu Takahashi <taka@valinux.co.jp>
To: mel@csn.ul.ie
Cc: matthew.e.tolentino@intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Avoiding fragmentation through different allocator
Date: Thu, 13 Jan 2005 17:02:18 +0900 (JST) [thread overview]
Message-ID: <20050113.170218.77038944.taka@valinux.co.jp> (raw)
In-Reply-To: <Pine.LNX.4.58.0501122247390.18142@skynet>
Hi Mel,
The global list looks interesting.
> > >Instead of having one global MAX_ORDER-sized array of free
> > >lists, there are
> > >three, one for each type of allocation. Finally, there is a
> > >list of pages of
> > >size 2^MAX_ORDER which is a global pool of the largest pages
> > >the kernel deals with.
> > is it so that the pages can
> > evolve according to system demands (assuming MAX_ORDER sized
> > chunks are eventually available again)?
> >
>
> Exactly. Once a 2^MAX_ORDER block has been merged again, it will not be
> reserved until the next split.
FYI, MAX_ORDER is huge in some architectures.
I guess another watermark should be introduced instead of MAX_ORDER.
Thanks,
Hirokazu Takahashi.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-01-13 8:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 22:45 Tolentino, Matthew E
2005-01-12 23:12 ` Mel Gorman
2005-01-13 8:02 ` Hirokazu Takahashi [this message]
2005-01-13 10:27 ` Mel Gorman
2005-01-16 4:03 ` Yasunori Goto
2005-01-16 16:21 ` Mel Gorman
2005-01-17 23:08 ` Yasunori Goto
2005-01-19 13:45 ` Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2005-01-17 16:48 Tolentino, Matthew E
2005-01-19 13:17 ` Mel Gorman
2005-01-12 21:09 Mel Gorman
2005-01-13 7:03 ` Matt Mackall
2005-01-13 7:20 ` Trond Myklebust
2005-01-13 10:22 ` Mel Gorman
2005-01-13 7:31 ` William Lee Irwin III
2005-01-13 10:11 ` Mel Gorman
2005-01-14 21:42 ` Marcelo Tosatti
2005-01-15 1:31 ` William Lee Irwin III
2005-01-15 19:19 ` Mel Gorman
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=20050113.170218.77038944.taka@valinux.co.jp \
--to=taka@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.e.tolentino@intel.com \
--cc=mel@csn.ul.ie \
/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