All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: david.vrabel@citrix.com, jgross@suse.com,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v3 (re-send)] xen/gntdev: Use mempolicy instead of VM_IO flag to avoid NUMA balancing
Date: Fri, 18 Nov 2016 08:59:47 +0100	[thread overview]
Message-ID: <20161118075947.GA5717@aepfle.de> (raw)
In-Reply-To: <1479413404-27332-1-git-send-email-boris.ostrovsky@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 292 bytes --]

On Thu, Nov 17, Boris Ostrovsky wrote:

> Commit 9c17d96500f7 ("xen/gntdev: Grant maps should not be subject to
> NUMA balancing") set VM_IO flag to prevent grant maps from being
> subjected to NUMA balancing.

Thanks, this works for me in 4.4:

Tested-by: Olaf Hering <olaf@aepfle.de>

Olaf

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Olaf Hering <olaf@aepfle.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: jgross@suse.com, xen-devel@lists.xenproject.org,
	david.vrabel@citrix.com, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 (re-send)] xen/gntdev: Use mempolicy instead of VM_IO flag to avoid NUMA balancing
Date: Fri, 18 Nov 2016 08:59:47 +0100	[thread overview]
Message-ID: <20161118075947.GA5717@aepfle.de> (raw)
In-Reply-To: <1479413404-27332-1-git-send-email-boris.ostrovsky@oracle.com>


[-- Attachment #1.1: Type: text/plain, Size: 292 bytes --]

On Thu, Nov 17, Boris Ostrovsky wrote:

> Commit 9c17d96500f7 ("xen/gntdev: Grant maps should not be subject to
> NUMA balancing") set VM_IO flag to prevent grant maps from being
> subjected to NUMA balancing.

Thanks, this works for me in 4.4:

Tested-by: Olaf Hering <olaf@aepfle.de>

Olaf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-18  8:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 20:10 [PATCH v3 (re-send)] xen/gntdev: Use mempolicy instead of VM_IO flag to avoid NUMA balancing Boris Ostrovsky
2016-11-18  7:59 ` Olaf Hering [this message]
2016-11-18  7:59   ` Olaf Hering
2016-11-18 21:51 ` Hugh Dickins
2016-11-18 21:51   ` Hugh Dickins
2016-11-18 22:14   ` Boris Ostrovsky
2016-11-18 22:14   ` Boris Ostrovsky
2016-11-18 22:14     ` Boris Ostrovsky
2016-11-18 22:27     ` Hugh Dickins
2016-11-18 22:27     ` Hugh Dickins
2016-11-18 22:27       ` Hugh Dickins
2016-11-18 22:49       ` Boris Ostrovsky
2016-11-18 22:49       ` Boris Ostrovsky
2016-11-18 22:49         ` Boris Ostrovsky
2016-11-18 23:27         ` Hugh Dickins
2016-11-18 23:27           ` Hugh Dickins
2016-11-18 23:27         ` Hugh Dickins
2016-11-18 21:51 ` Hugh Dickins
  -- strict thread matches above, loose matches on Subject: below --
2016-11-17 20:10 Boris Ostrovsky

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=20161118075947.GA5717@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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.