From: Stefan Bader <stefan.bader@canonical.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
roger.pau@citrix.com
Subject: Re: [PATCH v3] xen-blk(front|back): Handle large physical sector disks
Date: Wed, 22 May 2013 15:15:14 +0200 [thread overview]
Message-ID: <519CC4E2.90901@canonical.com> (raw)
In-Reply-To: <519CD44F02000078000D81B8@nat28.tlf.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2344 bytes --]
On 22.05.2013 14:21, Jan Beulich wrote:
>
> The only thing I haven't seen so far is a patch to the master
> copy of blkif.h to document the new xenstore node.
>
Ok, maybe something like this. What I realize is that I deliberately used
unsigned int as this is defined as 32bit on x86. But maybe it should be changed
to uint32_t?
-Stefan
From 8d1023ce11b9067346e9794d95b2876d98484f43 Mon Sep 17 00:00:00 2001
From: Stefan Bader <stefan.bader@canonical.com>
Date: Wed, 22 May 2013 15:11:18 +0200
Subject: [PATCH] blkif.h: Document the physical-sector-size extension
Signed-off-by: Stefan Bader <stefan.bader@canonical.com>
---
xen/include/public/io/blkif.h | 14 ++++++++++----
1 file changed, 10 insertions(+), 4 deletions(-)
diff --git a/xen/include/public/io/blkif.h b/xen/include/public/io/blkif.h
index 97b423b..f7c3366 100644
--- a/xen/include/public/io/blkif.h
+++ b/xen/include/public/io/blkif.h
@@ -208,12 +208,17 @@
* sector-size
* Values: <uint32_t>
*
- * The native sector size, in bytes, of the backend device.
+ * The logical sector size, in bytes, of the backend device.
+ *
+ * physical-sector-size
+ * Values: <unsigned int>
+ *
+ * The physical sector size, in bytes, of the backend device.
*
* sectors
* Values: <uint64_t>
*
- * The size of the backend device, expressed in units of its native
+ * The size of the backend device, expressed in units of its logical
* sector size ("sector-size").
*
*****************************************************************************
@@ -473,8 +478,9 @@
* NB. first_sect and last_sect in blkif_request_segment, as well as
* sector_number in blkif_request, are always expressed in 512-byte units.
* However they must be properly aligned to the real sector size of the
- * physical disk, which is reported in the "sector-size" node in the backend
- * xenbus info. Also the xenbus "sectors" node is expressed in 512-byte units.
+ * physical disk, which is reported in the "physical-sector-size" node in
+ * the backend xenbus info. Also the xenbus "sectors" node is expressed in
+ * 512-byte units.
*/
struct blkif_request_segment {
grant_ref_t gref; /* reference to I/O buffer frame */
--
1.7.9.5
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-05-22 13:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 17:47 [PATCH] xen-blk(front|back): Handle large physical sector disks Stefan Bader
2013-05-14 8:04 ` Jan Beulich
2013-05-15 9:26 ` Stefan Bader
2013-05-15 9:47 ` Jan Beulich
2013-05-15 10:04 ` James Harper
2013-05-15 10:10 ` Stefan Bader
2013-05-15 12:23 ` Jan Beulich
2013-05-15 13:54 ` Konrad Rzeszutek Wilk
2013-05-15 10:58 ` Stefan Bader
2013-05-15 12:28 ` Jan Beulich
2013-05-14 14:49 ` Roger Pau Monné
2013-05-14 16:11 ` Stefan Bader
2013-05-15 15:02 ` [PATCH v3] " Stefan Bader
2013-05-22 11:48 ` Stefan Bader
2013-05-22 12:21 ` Jan Beulich
2013-05-22 13:15 ` Stefan Bader [this message]
2013-05-22 13:22 ` Jan Beulich
2013-05-22 13:02 ` Konrad Rzeszutek Wilk
2013-05-28 12:47 ` Konrad Rzeszutek Wilk
2013-05-28 12:55 ` Stefan Bader
2013-05-28 16:17 ` Konrad Rzeszutek Wilk
2013-05-28 18:03 ` Stefan Bader
2013-06-05 20:25 ` 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=519CC4E2.90901@canonical.com \
--to=stefan.bader@canonical.com \
--cc=JBeulich@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).