From: "Justin T. Gibbs" <justing@spectralogic.com>
To: xen-devel@lists.xensource.com
Cc: Keir Fraser <keir@xen.org>
Subject: [PATCH 0 of 4 v3] blkif.h: Document protocol and existing extensions
Date: Mon, 20 Feb 2012 11:07:21 -0700 [thread overview]
Message-ID: <patchbomb.1329761241@ns1.eng.sldomain.com> (raw)
This patch series attempts to document the blkif PV interface and
the various extensions to it that are out in the wild.
Changes in v3:
patch 3 (blkif.h: Document the RedHat and Citrix blkif multi-page
ring extensions.):
o Mark the RedHat/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 RedHat and Citrix blkif multi-page
ring extensions.):
o Correct node names for the RedHat/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 reply other threads:[~2012-02-20 18:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 18:07 Justin T. Gibbs [this message]
2012-02-20 18:07 ` [PATCH 1 of 4 v3] blkif.h: Miscelaneous style fixes Justin T. Gibbs
2012-02-21 14:10 ` Konrad Rzeszutek Wilk
2012-02-21 14:15 ` Ian Campbell
2012-02-20 18:07 ` [PATCH 2 of 4 v3] blkif.h: Provide more complete documentation of the blkif interface Justin T. Gibbs
2012-02-21 14:10 ` Konrad Rzeszutek Wilk
2012-02-21 20:59 ` Justin T. Gibbs
2012-02-21 21:36 ` Konrad Rzeszutek Wilk
2012-02-22 11:14 ` Ian Campbell
2012-02-23 18:50 ` Konrad Rzeszutek Wilk
2012-02-23 22:41 ` Justin T. Gibbs
2012-02-21 14:27 ` Ian Campbell
2012-02-21 18:14 ` Justin T. Gibbs
2012-02-21 19:41 ` Ian Campbell
2012-02-20 18:07 ` [PATCH 3 of 4 v3] blkif.h: Document the RedHat and Citrix blkif multi-page ring extensions Justin T. Gibbs
2012-02-21 14:12 ` Konrad Rzeszutek Wilk
2012-02-21 14:32 ` Ian Campbell
2012-02-20 18:07 ` [PATCH 4 of 4 v3] blkif.h: Define and document the request number/size/segments extension Justin T. Gibbs
2012-02-21 14:22 ` Konrad Rzeszutek Wilk
2012-02-21 18:11 ` Justin T. Gibbs
2012-02-21 14:38 ` Ian Campbell
2012-02-21 18:03 ` Justin T. Gibbs
2012-02-21 19:42 ` Ian Campbell
2012-02-21 14:02 ` [PATCH 0 of 4 v3] blkif.h: Document protocol and existing extensions Konrad Rzeszutek Wilk
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=patchbomb.1329761241@ns1.eng.sldomain.com \
--to=justing@spectralogic.com \
--cc=keir@xen.org \
--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 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.