From: Keir Fraser <keir.xen@gmail.com>
To: "Justin T. Gibbs" <justing@spectralogic.com>,
xen-devel@lists.xensource.com
Subject: Re: [PATCH 0 of 4 v4] blkif.h: Document protocol and existing extensions
Date: Mon, 27 Feb 2012 06:50:29 +0000 [thread overview]
Message-ID: <CB70D835.2C505%keir.xen@gmail.com> (raw)
In-Reply-To: <patchbomb.1330324034@ns1.eng.sldomain.com>
On 27/02/2012 06:27, "Justin T. Gibbs" <justing@spectralogic.com> wrote:
> This patch series attempts to document the blkif PV interface and
> the various extensions to it that are out in the wild.
The previous round of these patches was already applied. They are sitting in
the staging tree currently (http://xenbits.xen.org/staging/xen-unstable.hg).
-- Keir
> Changes in v4:
>
> patch 2 (blkif.h: Provide more complete documentation of the blkif
> interface.):
> o Fix typo "discard-aligment" -> "discard-alignment"
> o Fix typo "unamp" -> "unmap"
> o Fix typo "formated" -> "formatted"
> o Clarify the text for "params".
> o Clarify the text for "sector-size".
>
> patch 4 (blkif.h: Define and document the request number/size/segments
> extension.)
> o Insert space in "Red Hat".
> o Clarify the text for "max-requests" in the backend section.
>
> Changes in v3:
>
> patch 3 (blkif.h: Document the Red Hat and Citrix blkif multi-page
> ring extensions.):
> o Mark the Red Hat/Amazon EC2 ring extension nodes as deprecated. While
> there is nothing fundamentally wrong with the method used there, it
> was not publicly documented (not even in patch form), and differs from
> the "page-order" large ring XenBus node convention used for other
> drivers.
>
> patch 4 (blkif.h: Define and document the request number/size/segments
> extension.)
> o Fix typo "max-ring_pages" -> "max-ring-pages".
>
> Changes in v2:
>
> patch 2 (blkif.h: Provide more complete documentation of the blkif
> interface.):
> o Mark backend device identification section as private to the
> backend driver.
> o Refer to docs/misc/vbd-interface.txt for the format of the
> virtual-device front-end node.
> o Correct field size for the virtual-device front-end node.
>
> patch 3 (blkif.h: Document the Red Hat and Citrix blkif multi-page
> ring extensions.):
> o Correct node names for the Red Hat/Amazon multi-ring extension. The
> previous patch mistakenly documented the now defunct FreeBSD extension.
> o Clarify the note on multi-page ring interoperability to indicate that
> identical ring parameters should be published to the XenStore for
> all supported schemes.
>
> v1 patch 4 (Deleted):
> o Remove patch that added the XEN_*_MAJOR definitions.
>
> patch 4 (blkif.h: Define and document the request number/size/segments
> extension.)
> o Bump __XEN_LATEST_INTERFACE_VERSION to 0x00040201 and use this version
> to guard the change to BLKIF_MAX_SEGMENTS_PER_REQUEST.
>
> --
> Justin
>
next prev parent reply other threads:[~2012-02-27 6:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 6:27 [PATCH 0 of 4 v4] blkif.h: Document protocol and existing extensions Justin T. Gibbs
2012-02-27 6:27 ` [PATCH 1 of 4 v4] blkif.h: Miscelaneous style fixes Justin T. Gibbs
2012-02-27 6:27 ` [PATCH 2 of 4 v4] blkif.h: Provide more complete documentation of the blkif interface Justin T. Gibbs
2012-02-27 6:27 ` [PATCH 3 of 4 v4] blkif.h: Document the Red Hat and Citrix blkif multi-page ring extensions Justin T. Gibbs
2012-02-27 6:27 ` [PATCH 4 of 4 v4] blkif.h: Define and document the request number/size/segments extension Justin T. Gibbs
2012-02-27 6:50 ` Keir Fraser [this message]
2012-02-27 9:53 ` [PATCH 0 of 4 v4] blkif.h: Document protocol and existing extensions Ian Campbell
2012-02-27 14:40 ` Justin T. Gibbs
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=CB70D835.2C505%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=justing@spectralogic.com \
--cc=xen-devel@lists.xensource.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).