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: Wed, 17 Sep 2003 12:32:02 -0700 [thread overview]
Message-ID: <20030917193202.GG14079@holomorphy.com> (raw)
In-Reply-To: <200309171326.11848.lmb@exatas.unisinos.br>
On Wed, Sep 17, 2003 at 01:26:11PM -0300, Leandro Motta Barros wrote:
> Thanks for the feedback on the previous email. Well, there is another
> thing we thought that could be done. '__vmalloc()' allocates its
> memory by calling 'alloc_page()' for every necessary page. Wouldn't
> it be better calling 'alloc_pages()' to allocate more pages at once
> whenever possible? We would need more bookeepping, and sometimes it
> could be necessary to actually allocate the memory page per page, but
> we think this approach could be a way to use memory blocks of higher order.
> Do you think this is feasible or useful?
> Also, we would like to know if you have suggestions on topics that we could
> explore and implement.
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.
-- 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>
next prev parent reply other threads:[~2003-09-17 19:32 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 [this message]
2003-09-18 16:20 ` Leandro Motta Barros
2003-09-18 17:08 ` William Lee Irwin III
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=20030917193202.GG14079@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