qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: aliguori@us.ibm.com, mst@redhat.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
Subject: Re: [Qemu-devel] [PULL v4 08/11] rdma: core logic
Date: Thu, 18 Apr 2013 20:35:38 -0400	[thread overview]
Message-ID: <5170915A.8050907@linux.vnet.ibm.com> (raw)
In-Reply-To: <51706FDA.3050609@redhat.com>

On 04/18/2013 06:12 PM, Eric Blake wrote:
> On 04/17/2013 05:07 PM, mrhines@linux.vnet.ibm.com wrote:
>> From: "Michael R. Hines" <mrhines@us.ibm.com>
>>
>> Code that does need to be visible is kept
>> well contained inside this file and this is the only
>> new additional file to the entire patch - good
>> progress.
>>
>> This file includes the entire protocol and interfaces
>> required to perform RDMA migration.
>>
>> Also, the configure and Makefile modifications to link
>> this file are included.
>>
>> Full documentation is in docs/rdma.txt
> Which doesn't appear until later in the series?  If a git bisect lands
> on this patch, I have to go out of my way to find the later commit that
> adds the docs.
>
> I personally like series that put the docs FIRST.  On initial review,
> that gives the docs a chance for a clean-room review untainted by the
> implementation choices; and leaves the docs fresh in reviewers' minds
> during the rest of the series to validate that the implementation
> matches docs.  On later review (such as git bisect landing here), it
> means the docs are in-tree for any other commit that references them.
> If it were me, I'd rebase things to put docs in patch 1 on the v5 series.
>

No problem. Will do.

  reply	other threads:[~2013-04-19  0:36 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 23:07 [Qemu-devel] [PULL v4 00/11] rdma: migration support mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 01/11] rdma: export yield_until_fd_readable() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 02/11] rdma: introduce qemu_ram_foreach_block() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 03/11] rdma: introduce qemu_file_mode_is_not_valid() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 04/11] rdma: export ram_handle_compressed() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 05/11] rdma: export qemu_fflush() mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 06/11] rdma: new QEMUFileOps hooks mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 07/11] rdma: introduce capability for chunk registration mrhines
2013-04-18 22:07   ` Eric Blake
2013-04-19  0:34     ` Michael R. Hines
2013-04-20 17:02     ` Michael S. Tsirkin
2013-04-21 13:19       ` Paolo Bonzini
2013-04-21 14:17         ` Michael S. Tsirkin
2013-04-21 17:19           ` Michael R. Hines
2013-04-21 19:13             ` Michael S. Tsirkin
2013-04-21 16:05         ` Michael R. Hines
2013-04-21 18:59           ` Michael S. Tsirkin
2013-04-21 19:55             ` Michael R. Hines
2013-04-21 16:06         ` Michael R. Hines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 08/11] rdma: core logic mrhines
2013-04-18  7:55   ` Paolo Bonzini
2013-04-18 13:57     ` Michael R. Hines
2013-04-18  7:58   ` Michael S. Tsirkin
2013-04-18 13:59     ` Michael R. Hines
2013-04-18 13:06       ` Michael S. Tsirkin
2013-04-18 14:14         ` Michael R. Hines
2013-04-18 13:32           ` Michael S. Tsirkin
2013-04-18 14:45             ` Michael R. Hines
2013-04-18 13:52               ` Michael S. Tsirkin
2013-04-18 15:14                 ` Anthony Liguori
2013-04-18 14:53             ` [Qemu-devel] licensing of IBM contributions to QEMU (was Re: [PULL v4 08/11] rdma: core logic) Paolo Bonzini
2013-04-18 19:15               ` Michael R. Hines
2013-04-19  0:35               ` Anthony Liguori
2013-04-18  8:44   ` [Qemu-devel] [PULL v4 08/11] rdma: core logic Orit Wasserman
2013-04-18 13:54     ` Michael R. Hines
2013-04-18 15:51       ` Orit Wasserman
2013-04-18 19:41         ` Michael R. Hines
2013-04-18 22:12   ` Eric Blake
2013-04-19  0:35     ` Michael R. Hines [this message]
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 09/11] rdma: send pc.ram mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 10/11] rdma: print out throughput while debugging mrhines
2013-04-17 23:07 ` [Qemu-devel] [PULL v4 11/11] rdma: add documentation mrhines
2013-04-18  6:55   ` Michael S. Tsirkin
2013-04-19  0:57     ` Michael R. Hines
2013-04-17 23:39 ` [Qemu-devel] [PULL v4 00/11] rdma: migration support Anthony Liguori
2013-04-18 13:46   ` Michael R. Hines
2013-04-18  7:00 ` Michael S. Tsirkin
2013-04-18 13:49   ` Michael R. Hines
2013-04-18 13:50     ` Michael S. Tsirkin
2013-04-18 19:17       ` Michael R. Hines
2013-04-18 20:12         ` Michael S. Tsirkin
2013-04-18 21:28           ` Michael R. Hines
2013-04-18 20:33             ` Michael S. Tsirkin
2013-04-18 14:36   ` 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=5170915A.8050907@linux.vnet.ibm.com \
    --to=mrhines@linux.vnet.ibm.com \
    --cc=abali@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=eblake@redhat.com \
    --cc=gokul@us.ibm.com \
    --cc=mrhines@us.ibm.com \
    --cc=mst@redhat.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).