From: Paolo Bonzini <pbonzini@redhat.com>
To: Chegu Vinod <chegu_vinod@hp.com>
Cc: Karen Noel <knoel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Juan Jose Quintela Carreira <quintela@redhat.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
"Michael R. Hines" <mrhines@linux.vnet.ibm.com>,
Orit Wasserman <owasserm@redhat.com>,
"Michael R. Hines" <mrhines@us.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH v6 00/11] rdma: migration support
Date: Fri, 10 May 2013 09:58:06 +0200 [thread overview]
Message-ID: <518CA88E.50002@redhat.com> (raw)
In-Reply-To: <518C2135.306@hp.com>
Il 10/05/2013 00:20, Chegu Vinod ha scritto:
>>
>> Wow, I didn't know that either. Perhaps this must be causing the
>> entire QEMU process and its threads to seize up.
>>
>> It may be necessary to run the pinning command *outside* of QEMU's I/O
>> lock in a separate thread if it's really that much overhead.
>
> Not really sure if the BQL is causing the freeze...but in general
> pinning of all memory when the guest is run is perhaps not the best
> choice for large enterprise class guests...i.e. its better to do it as
> part of the start of the guest.
If pinning is done in the setup phase, it should run outside the BQL.
Paolo
next prev parent reply other threads:[~2013-05-10 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 23:28 [Qemu-devel] [PATCH v6 00/11] rdma: migration support Chegu Vinod
2013-05-09 17:20 ` Michael R. Hines
2013-05-09 22:20 ` Chegu Vinod
2013-05-09 22:45 ` Michael R. Hines
2013-06-02 4:09 ` Michael R. Hines
2013-06-06 23:51 ` Chegu Vinod
2013-06-07 5:38 ` Michael R. Hines
2013-05-10 7:58 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-04-24 19:00 mrhines
2013-04-24 21:50 ` Paolo Bonzini
2013-04-24 23:48 ` Michael R. Hines
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=518CA88E.50002@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chegu_vinod@hp.com \
--cc=knoel@redhat.com \
--cc=mrhines@linux.vnet.ibm.com \
--cc=mrhines@us.ibm.com \
--cc=mst@redhat.com \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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 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.