From: Ruthiano Simioni Munaretti <ruthiano@exatas.unisinos.br>
To: linux-mm@kvack.org
Cc: sisopiii-l@cscience.org, lmb@exatas.unisinos.br
Subject: Non-contiguous memory allocation
Date: Mon, 20 Oct 2003 14:00:59 -0200 [thread overview]
Message-ID: <200310201400.59334.ruthiano@exatas.unisinos.br> (raw)
Hello folks!
Two months ago, you suggest us an interface implementation in non-contiguous
memory allocation:
William Lee Irwin III wrote:
> 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.)
Our question: there are (or --> there was... :) any work in this area?
Somebody tried to implement this?
Also, do you have any suggestions on how to measure the benefits of this
approach once it is implemented? For example, which metrics should be used
and which tools can we use to measure them?
Thanks!
LMB, Ruthiano.
--
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>
reply other threads:[~2003-10-20 16:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200310201400.59334.ruthiano@exatas.unisinos.br \
--to=ruthiano@exatas.unisinos.br \
--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