From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Roland Dreier <roland@kernel.org>,
qemu-devel@nongnu.org,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Yishai Hadas <yishaih@mellanox.com>,
LKML <linux-kernel@vger.kernel.org>,
Hal Rosenstock <hal.rosenstock@gmail.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>,
Sean Hefty <sean.hefty@intel.com>,
Christoph Lameter <cl@linux.com>
Subject: Re: [Qemu-devel] [PATCHv2] rdma: add a new IB_ACCESS_GIFT flag
Date: Wed, 10 Apr 2013 00:32:31 -0400 [thread overview]
Message-ID: <5164EB5F.80403@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130410032449.GA12777@redhat.com>
On 04/09/2013 11:24 PM, Michael S. Tsirkin wrote:
> Which mechanism do you refer to? You patches still seem to pin each
> page in guest memory at some point, which will break all COW. In
> particular any pagemap tricks to detect duplicates on source that I
> suggested won't work.
Sorry, I mispoke. I'm reffering to dynamic server page registration.
Of course it does not eliminate pinning - but it does mitigate the foot
print of the VM as a feature that was requested.
I have implemented it and documented it.
- Michael
>> On 04/09/2013 03:03 PM, Michael S. Tsirkin wrote:
>>> presumably is_dup_page reads the page, so should not break COW ...
>>>
>>> I'm not sure about the cgroups swap limit - you might have
>>> too many non COW pages so attempting to fault them all in
>>> makes you exceed the limit. You really should look at
>>> what is going on in the pagemap, to see if there's
>>> measureable gain from the patch.
>>>
>>>
>>> On Fri, Apr 05, 2013 at 05:32:30PM -0400, Michael R. Hines wrote:
>>>> Well, I have the "is_dup_page()" commented out.......when RDMA is
>>>> activated.....
>>>>
>>>> Is there something else in QEMU that could be touching the page that
>>>> I don't know about?
>>>>
>>>> - Michael
>>>>
>>>>
>>>> On 04/05/2013 05:03 PM, Roland Dreier wrote:
>>>>> On Fri, Apr 5, 2013 at 1:51 PM, Michael R. Hines
>>>>> <mrhines@linux.vnet.ibm.com> wrote:
>>>>>> Sorry, I was wrong. ignore the comments about cgroups. That's still broken.
>>>>>> (i.e. trying to register RDMA memory while using a cgroup swap limit cause
>>>>>> the process get killed).
>>>>>>
>>>>>> But the GIFT flag patch works (my understanding is that GIFT flag allows the
>>>>>> adapter to transmit stale memory information, it does not have anything to
>>>>>> do with cgroups specifically).
>>>>> The point of the GIFT patch is to avoid triggering copy-on-write so
>>>>> that memory doesn't blow up during migration. If that doesn't work
>>>>> then there's no point to the patch.
>>>>>
>>>>> - R.
>>>>>
next prev parent reply other threads:[~2013-04-10 4:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 15:51 [Qemu-devel] [PATCHv2] rdma: add a new IB_ACCESS_GIFT flag Michael S. Tsirkin
2013-04-02 15:51 ` Michael S. Tsirkin
2013-04-02 16:57 ` Roland Dreier
2013-04-02 17:05 ` Michael S. Tsirkin
2013-04-02 22:17 ` Michael R. Hines
2013-04-03 16:07 ` Michael S. Tsirkin
2013-04-05 20:17 ` Michael R. Hines
2013-04-05 20:43 ` Roland Dreier
2013-04-05 20:51 ` Michael R. Hines
2013-04-05 21:03 ` Roland Dreier
2013-04-05 21:32 ` Michael R. Hines
2013-04-09 19:03 ` Michael S. Tsirkin
2013-04-10 1:26 ` Michael R. Hines
2013-04-10 3:24 ` Michael S. Tsirkin
2013-04-10 4:32 ` Michael R. Hines [this message]
2013-04-10 5:32 ` Michael S. Tsirkin
2013-04-10 15:48 ` Michael R. Hines
2013-04-10 15:05 ` Michael S. Tsirkin
2013-04-10 16:28 ` Michael R. Hines
2013-04-09 19:09 ` Michael S. Tsirkin
2013-04-05 20:54 ` Michael R. Hines
2013-04-09 16:39 ` Michael S. Tsirkin
2013-04-09 17:56 ` Michael R. Hines
2013-04-09 19:00 ` Michael S. Tsirkin
2013-04-09 19:12 ` Michael S. Tsirkin
2013-04-09 20:34 ` Michael S. Tsirkin
2013-04-09 20:37 ` Michael S. Tsirkin
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=5164EB5F.80403@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=cl@linux.com \
--cc=hal.rosenstock@gmail.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.com \
--cc=yishaih@mellanox.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;
as well as URLs for NNTP newsgroup(s).