All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: konrad.wilk@oracle.com, david.vrabel@citrix.com,
	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, 10 Nov 2016 17:42:26 +0100	[thread overview]
Message-ID: <20161110164226.GA5937@aepfle.de> (raw)
In-Reply-To: <0c993a89-83a1-d8a8-4927-d36660179256@oracle.com>

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

On Thu, Nov 10, Boris Ostrovsky wrote:

> Is this something new? Because this patch has been there for a year.

It was just tested now, cycling through all the combinations for a
disk=[]. Removing "direct-is-save" will use different code paths and the
error is not seen.

Olaf

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

  parent reply	other threads:[~2016-11-10 16:42 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 ` [Xen-devel] " David Vrabel
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:39   ` [Xen-devel] " Boris Ostrovsky
2016-11-10 16:42     ` Olaf Hering
2016-11-10 16:42     ` Olaf Hering [this message]
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             ` Boris Ostrovsky
2016-11-10 17:49           ` David Vrabel
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=20161110164226.GA5937@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.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.