From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<konrad.wilk@oracle.com>, <david.vrabel@citrix.com>
Cc: <linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
<xen-devel@lists.xen.org>
Subject: Re: [Xen-devel] [PATCH RESEND] xen/gntdev: Grant maps should not be subject to NUMA balancing
Date: Thu, 26 Nov 2015 17:48:15 +0000 [thread overview]
Message-ID: <565745DF.8030008@citrix.com> (raw)
In-Reply-To: <1447186233-3194-1-git-send-email-boris.ostrovsky@oracle.com>
On 10/11/15 20:10, Boris Ostrovsky wrote:
> Doing so will cause the grant to be unmapped and then, during
> fault handling, the fault to be mistakenly treated as NUMA hint
> fault.
>
> In addition, even if those maps could partcipate in NUMA
> balancing, it wouldn't provide any benefit since we are unable
> to determine physical page's node (even if/when VNUMA is
> implemented).
>
> Marking grant maps' VMAs as VM_IO will exclude them from being
> part of NUMA balancing.
Applied to for-linus-4.4, thanks.
David
next prev parent reply other threads:[~2015-11-26 17:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 20:10 [PATCH RESEND] xen/gntdev: Grant maps should not be subject to NUMA balancing Boris Ostrovsky
2015-11-26 17:48 ` David Vrabel [this message]
2015-11-26 17:48 ` David Vrabel
2016-11-10 16:26 ` [Xen-devel] " Olaf Hering
2016-11-10 16:39 ` Boris Ostrovsky
2016-11-10 16:42 ` Olaf Hering
2016-11-10 17:34 ` Boris Ostrovsky
2016-11-10 17:34 ` [Xen-devel] " Boris Ostrovsky
2016-11-10 17:47 ` Olaf Hering
2016-11-10 17:47 ` [Xen-devel] " Olaf Hering
2016-11-10 17:49 ` David Vrabel
2016-11-10 18:09 ` Boris Ostrovsky
2016-11-10 18:09 ` [Xen-devel] " Boris Ostrovsky
2016-11-10 17:49 ` David Vrabel
2016-11-10 16:42 ` Olaf Hering
2016-11-10 16:39 ` Boris Ostrovsky
2016-11-10 16:26 ` Olaf Hering
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=565745DF.8030008@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.