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
Subject: Re: [PATCH v2] xen/gntdev: Use mempolicy instead of VM_IO flag to avoid NUMA balancing
Date: Thu, 17 Nov 2016 12:28:44 +0100 [thread overview]
Message-ID: <20161117112843.GA19761@aepfle.de> (raw)
In-Reply-To: <1479318378-595-1-git-send-email-boris.ostrovsky@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
On Wed, Nov 16, Boris Ostrovsky wrote:
> Unfortunately I haven't been able to trigger NUMA balancing
> so while I tested this in general I am not sure I actually
> exercised the code path.
Thanks for the patch!
Would be nice to actually test the code path which caused the initial
addition of VM_IO. I think I lack the hardware to excersise them.
In my 4.4 based sources I get the following unresolved symbols. If that
happens to work in mainline the failures should at least be considered
during backporting of this proposed patch to the stable trees.
ERROR: "__mpol_dup" [drivers/xen/xen-gntdev.ko] undefined!
ERROR: "get_task_policy" [drivers/xen/xen-gntdev.ko] undefined!
Appearently these symbols lack just an EXPORT_SYMBOL_GPL.
Olaf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2016-11-17 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 17:46 [PATCH v2] xen/gntdev: Use mempolicy instead of VM_IO flag to avoid NUMA balancing Boris Ostrovsky
2016-11-17 11:28 ` Olaf Hering [this message]
2016-11-17 16:01 ` Boris Ostrovsky
2016-11-17 16:01 ` Boris Ostrovsky
2016-11-17 16:01 ` Olaf Hering
2016-11-17 16:01 ` Olaf Hering
2016-11-17 16:09 ` Boris Ostrovsky
2016-11-17 16:09 ` Boris Ostrovsky
2016-11-17 11:28 ` Olaf Hering
-- strict thread matches above, loose matches on Subject: below --
2016-11-16 17:46 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=20161117112843.GA19761@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=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.