From: William Lee Irwin III <wli@holomorphy.com>
To: Leandro Motta Barros <lmb@exatas.unisinos.br>
Cc: linux-mm@kvack.org, sisopiii-l@cscience.org
Subject: Re: __vmalloc and alloc_page
Date: Thu, 18 Sep 2003 10:08:56 -0700 [thread overview]
Message-ID: <20030918170856.GT14079@holomorphy.com> (raw)
In-Reply-To: <200309181320.08605.lmb@exatas.unisinos.br>
On Wednesday 17 September 2003 16:32, William Lee Irwin III wrote:
>> Higher-order would probably not be as useful as you'd suspect; try
>> looking at the distribution of available pages of given sizes in /proc/.
>> OTOH, just being able to get more than one page in one call (not relying
>> on physically contiguous memory) would be a simple and useful optimization.
On Thu, Sep 18, 2003 at 01:20:08PM -0300, Leandro Motta Barros wrote:
> I'm not sure if I really understood what you said. Does it means that in some
> cases (e.g., when the buddy allocator has a free chunk of the proper size)
> this could be good, even though this will not help other things (like
> reducing the number of splits in the buddy allocator)?
No.
Relying on there being contiguous memory means it will fail more often
than it has to and/or does now.
The suggestion was to add an interface to fetch more than one page in
one call, to reduce various kinds of overheads associated with the round
trip through the codepaths (dis/re -enabling ints, ticking counters, etc.)
-- wli
--
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>
prev parent reply other threads:[~2003-09-18 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 16:26 Leandro Motta Barros
2003-09-17 17:19 ` Ravi Krishnamurthy
2003-09-17 19:32 ` William Lee Irwin III
2003-09-18 16:20 ` Leandro Motta Barros
2003-09-18 17:08 ` William Lee Irwin III [this message]
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=20030918170856.GT14079@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-mm@kvack.org \
--cc=lmb@exatas.unisinos.br \
--cc=sisopiii-l@cscience.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