From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Steven Noonan <steven@uplinklabs.net>,
Mel Gorman <mgorman@suse.de>,
Cyrill Gorcunov <gorcunov@gmail.com>,
David Vrabel <david.vrabel@citrix.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>, Rik van Riel <riel@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Linux-MM <linux-mm@kvack.org>, Linux-X86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Pavel Emelyanov <xemul@parallels.com>
Subject: Re: [PATCH 2/3] x86: Define _PAGE_NUMA with unused physical address bits PMD and PTE levels
Date: Tue, 08 Apr 2014 09:16:49 -0700 [thread overview]
Message-ID: <534420F1.3030301@zytor.com> (raw)
In-Reply-To: <20140408160250.GE31554@phenom.dumpdata.com>
On 04/08/2014 09:02 AM, Konrad Rzeszutek Wilk wrote:
>>>
>>> Amazon EC2 does have large memory instance types with NUMA exposed to
>>> the guest (e.g. c3.8xlarge, i2.8xlarge, etc), so it'd be preferable
>>> (to me anyway) if we didn't require !XEN.
>
> What about the patch that David Vrabel posted:
>
> http://osdir.com/ml/general/2014-03/msg41979.html
>
> Has anybody taken it for a spin?
>
Oh lovely, more pvops in low level paths. I'm so thrilled.
Incidentally, I wasn't even Cc:'d on that patch and was only added to
the thread by Linus, but never saw the early bits of the thread
including the actual patch.
-hpa
--
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>
next prev parent reply other threads:[~2014-04-08 16:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 15:10 [RFC PATCH 0/3] Use an alternative to _PAGE_PROTNONE for _PAGE_NUMA Mel Gorman
2014-04-07 15:10 ` [PATCH 1/3] x86: Require x86-64 for automatic NUMA balancing Mel Gorman
2014-04-07 15:10 ` [PATCH 2/3] x86: Define _PAGE_NUMA with unused physical address bits PMD and PTE levels Mel Gorman
2014-04-07 15:32 ` David Vrabel
2014-04-07 15:49 ` Mel Gorman
2014-04-07 16:19 ` Cyrill Gorcunov
2014-04-07 18:28 ` Mel Gorman
2014-04-07 19:16 ` Cyrill Gorcunov
2014-04-07 19:27 ` H. Peter Anvin
2014-04-07 19:36 ` Cyrill Gorcunov
2014-04-07 19:42 ` H. Peter Anvin
2014-04-07 21:25 ` Mel Gorman
2014-04-08 4:04 ` Steven Noonan
2014-04-08 15:16 ` H. Peter Anvin
2014-04-08 16:02 ` Konrad Rzeszutek Wilk
2014-04-08 16:16 ` H. Peter Anvin [this message]
2014-04-08 16:47 ` Mel Gorman
2014-04-08 16:50 ` David Vrabel
2014-04-08 16:51 ` Mel Gorman
2014-04-09 15:18 ` Konrad Rzeszutek Wilk
2014-04-09 15:39 ` Mel Gorman
2014-04-08 20:51 ` Steven Noonan
2014-04-08 20:59 ` H. Peter Anvin
2014-04-09 15:04 ` Konrad Rzeszutek Wilk
2014-04-09 15:09 ` Peter Zijlstra
2014-04-08 9:31 ` David Vrabel
2014-04-07 21:19 ` Mel Gorman
2014-04-07 17:37 ` Dave Hansen
2014-04-07 15:10 ` [PATCH 3/3] mm: Allow FOLL_NUMA on FOLL_FORCE Mel Gorman
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=534420F1.3030301@zytor.com \
--to=hpa@zytor.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david.vrabel@citrix.com \
--cc=gorcunov@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=steven@uplinklabs.net \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xemul@parallels.com \
/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