From: Tejun Heo <teheo@novell.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: remap allocator for per-CPU memory
Date: Wed, 13 May 2009 19:09:52 +0900 [thread overview]
Message-ID: <4A0A9C70.6090803@novell.com> (raw)
In-Reply-To: <4A09991E.9010903@kernel.org>
Tejun Heo wrote:
> Jan Beulich wrote:
>> Didn't the addition of this allocator introduce another case that
>> needs special treatment in pageattr.c? Since large pages are used
>> for mapping the allocated memory, but only part of the initially
>> allocated large pages are actually retained, there's now the
>> potential for TLB aliases with different cache attributes for those
>> parts of these pages that get passed back through free_bootmem().
>
> Hmmm.... yes, the large page mapping and the returned part of it would
> alias each other. What changes should be made for it? Dunno much
> about how pageattr works.
Okay, just glanced over the pageattr code. I don't think we need any
special provisions for this as long as the TLB is fine with having
overlapping PMD and PTE mappings with different attributes (please
note that these two mappings aren't occupying the same linear
addresses - they're aliases). This is allowed, right?
Thanks.
--
tejun
next prev parent reply other threads:[~2009-05-13 10:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:30 remap allocator for per-CPU memory Jan Beulich
2009-05-12 15:43 ` Tejun Heo
2009-05-13 10:09 ` Tejun Heo [this message]
2009-05-13 11:05 ` Andi Kleen
2009-05-13 11:13 ` Tejun Heo
2009-05-13 11:29 ` Tejun Heo
2009-05-13 11:46 ` Andi Kleen
2009-05-13 12:51 ` Jan Beulich
[not found] ` <4A0ADE6A0200007800000BA7@novell.com>
2009-05-13 13:29 ` Tejun Heo
2009-05-13 13:44 ` Jan Beulich
2009-05-13 13:53 ` Tejun Heo
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=4A0A9C70.6090803@novell.com \
--to=teheo@novell.com \
--cc=JBeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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