From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: aliguori@us.ibm.com, quintela@redhat.com, qemu-devel@nongnu.org,
owasserm@redhat.com, abali@us.ibm.com, mrhines@us.ibm.com,
gokul@us.ibm.com, pbonzini@redhat.com, chegu_vinod@hp.com,
knoel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v3 resend/cleanup 1/8] rdma: update documentation to reflect new unpin support
Date: Fri, 12 Jul 2013 13:46:04 -0400 [thread overview]
Message-ID: <51E040DC.6040500@linux.vnet.ibm.com> (raw)
In-Reply-To: <51E03F4C.9040506@redhat.com>
On 07/12/2013 01:39 PM, Eric Blake wrote:
> On 07/12/2013 11:26 AM, Michael R. Hines wrote:
>> On 07/12/2013 01:09 PM, Eric Blake wrote:
>>> On 07/12/2013 08:40 AM, mrhines@linux.vnet.ibm.com wrote:
>>>> From: "Michael R. Hines" <mrhines@us.ibm.com>
>>>>
>>>> As requested, the protocol now includes memory unpinning support.
>>>> This has been implemented in a non-optimized manner, in such a way
>>>> that one could devise an LRU or other workload-specific information
>>>> on top of the basic mechanism to influence the way unpinning happens
>>>> during runtime.
>>>>
>>>> ++++++++++++++++++++++++++++++---------------------
>>>> 1 file changed, 30 insertions(+), 21 deletions(-)
>>> I suggest splitting this patch into two; and cc-ing the first of the two
>>> patches through qemu-trivial (since formatting cleanups can be applied
>>> now, even while still waiting for a comprehensive review of the
>>> algorithm in the rest of the series)
>> My understanding is that the reviews have completed already,
>> including a very extensive test series that I performed which
>> included both virt-test results and non-virt-test results from both
>> myself and Chegu.
>>
>> Am I mistaken?
> It may have been reviewed and tested, but as you just barely posted v3
> today and there is not yet a maintainer's queue with a PULL request, it
> is still subject to any further review that people want to provide, and
> up to the maintainer to state definitively if the further review
> comments must be addressed. It's not the end of the world if you don't
> split this patch, but at the same time, splitting it makes it easier to
> review, and to pick and choose which parts get backported (trivial
> formatting vs. new feature).
>
Alright - I'll wait until next week before re-sending again. No big deal.
Juan? Ping?
- Michael
next prev parent reply other threads:[~2013-07-12 17:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 14:40 [Qemu-devel] [PATCH v3 resend/cleanup 0/8] rdma: core logic mrhines
2013-07-12 14:40 ` [Qemu-devel] [PATCH v3 resend/cleanup 1/8] rdma: update documentation to reflect new unpin support mrhines
2013-07-12 17:09 ` Eric Blake
2013-07-12 17:26 ` Michael R. Hines
2013-07-12 17:39 ` Eric Blake
2013-07-12 17:46 ` Michael R. Hines [this message]
2013-07-12 14:40 ` [Qemu-devel] [PATCH v3 resend/cleanup 2/8] rdma: bugfix: ram_control_save_page() mrhines
2013-07-12 17:09 ` Eric Blake
2013-07-12 14:40 ` [Qemu-devel] [PATCH v3 resend/cleanup 3/8] rdma: introduce ram_handle_compressed() mrhines
2013-07-12 14:40 ` [Qemu-devel] [PATCH v3 resend/cleanup 4/8] rdma: core logic mrhines
2013-07-12 14:40 ` [Qemu-devel] [PATCH v3 resend/cleanup 5/8] rdma: send pc.ram mrhines
2013-07-12 14:40 ` [Qemu-devel] [PATCH v3 resend/cleanup 6/8] rdma: allow state transitions between other states besides ACTIVE mrhines
2013-07-12 14:40 ` [Qemu-devel] [PATCH v3 resend/cleanup 7/8] rdma: introduce MIG_STATE_NONE and change MIG_STATE_SETUP state transition mrhines
2013-07-12 14:40 ` [Qemu-devel] [PATCH v3 resend/cleanup 8/8] rdma: account for the time spent in MIG_STATE_SETUP through QMP mrhines
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=51E040DC.6040500@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=abali@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=chegu_vinod@hp.com \
--cc=eblake@redhat.com \
--cc=gokul@us.ibm.com \
--cc=knoel@redhat.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@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 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).