From: Andi Kleen <ak@suse.de>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: Dave McCracken <dmccr@us.ibm.com>,
'Hugh Dickins' <hugh@veritas.com>,
'Andrew Morton' <akpm@osdl.org>,
linux-mm@kvack.org
Subject: Re: [patch] shared page table for hugetlb page
Date: Thu, 8 Jun 2006 09:31:13 +0200 [thread overview]
Message-ID: <200606080931.13481.ak@suse.de> (raw)
In-Reply-To: <000201c68a9c$635ba700$d534030a@amr.corp.intel.com>
On Thursday 08 June 2006 03:39, Chen, Kenneth W wrote:
> Andi Kleen wrote on Wednesday, June 07, 2006 6:25 PM
> > > @@ -18,16 +18,102 @@
> > > #include <asm/tlb.h>
> > > #include <asm/tlbflush.h>
> > >
> > > +#ifdef CONFIG_X86_64
> >
> > Why is this done for x86-64 only?
>
>
> Do you mean not for i386? I'm too chicken to do it for 32-bit PAE mode. There
> are tons of other issue that application has to fight through with highmem and
> playing with only limited 32-bit virtual address space, I thought this usage
> might be very limited for 32-bit x86.
I don't see how highmem should make any difference for shared ptes though.
The ptes can be in highmem, but you should handle this already.
Of course highmem by itself is unpleasant, but it shouldn't affect this
particular problem much.
-Andi
--
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:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2006-06-08 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-07 20:51 Chen, Kenneth W
2006-06-08 1:25 ` Andi Kleen
2006-06-08 1:39 ` Chen, Kenneth W
2006-06-08 7:31 ` Andi Kleen [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=200606080931.13481.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dmccr@us.ibm.com \
--cc=hugh@veritas.com \
--cc=kenneth.w.chen@intel.com \
--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