From: Dave Hansen <haveblue@us.ibm.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: lhms-devel@lists.sourceforge.net, linux-mm@kvack.org
Subject: Re: [Lhms-devel] Re: [RFC] sparsemem patches (was nonlinear)
Date: Thu, 28 Oct 2004 09:52:42 -0700 [thread overview]
Message-ID: <418123DA.1090609@us.ibm.com> (raw)
In-Reply-To: <41811F3A.1090706@shadowen.org>
Andy Whitcroft wrote:
> Dave Hansen wrote:
>> Have you given any thought to using virt_to_page(page)->foo method to
>> store section information instead of using page->flags? It seems
>> we're already sucking up page->flags left and right, and I'd hate to
>> consume that many more.
>
> As Martin indicates we don't use any more flags on the bit challenged
> arches where this would be an issue.
Could you explain a little bit how the section is encoded in there, and
what kind of limits there are? How many free bits do you need, and are
there implications when it grows or shrinks as new PG_flags are added?
> The little trick you used has some
> overhead to it, and current testing is showing an unexpected performance
> improvement with this stack.
Does my little trick just have an anticipated performance impact, or a
measured one?
--
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:[~2004-10-28 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <098973549.shadowen.org>
2004-10-28 16:04 ` Dave Hansen
2004-10-28 16:19 ` Martin J. Bligh
2004-10-28 16:32 ` Andy Whitcroft
2004-10-28 16:52 ` Dave Hansen [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=418123DA.1090609@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=apw@shadowen.org \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-mm@kvack.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