All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Keir Fraser <Keir.Fraser@eu.citrix.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1 of 2] blkfront: sector size > 512
Date: Fri, 22 May 2009 15:31:28 +0100	[thread overview]
Message-ID: <4A16B740.90809@eu.citrix.com> (raw)
In-Reply-To: <C63AA5FE.6E47%keir.fraser@eu.citrix.com>

Keir Fraser wrote:

> 
> Yeah, I'd take a patch to add a nice clear comment about this to blkif.h.
> ;-)
> 



Is this comment clear enough?

Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>

---


diff -r 61404d971c92 xen/include/public/io/blkif.h
--- a/xen/include/public/io/blkif.h	Thu May 21 04:31:47 2009 +0100
+++ b/xen/include/public/io/blkif.h	Fri May 22 15:29:19 2009 +0100
@@ -84,6 +84,13 @@
  */
 #define BLKIF_MAX_SEGMENTS_PER_REQUEST 11
 
+/* 
+ * first_sect and last_sect in blkif_request_segment, as well as
+ * sector_number in blkif_request are all expressed in 512 bytes units,
+ * however they must be properly aligned to the real sector size of
+ * the physical disk (as reported in the "sector-size" node in backend
+ * xenbus info).
+ */
 struct blkif_request_segment {
     grant_ref_t gref;        /* reference to I/O buffer frame        */
     /* @first_sect: first sector in frame to transfer (inclusive).   */

  reply	other threads:[~2009-05-22 14:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 11:40 [PATCH 1 of 2] blkfront: sector size > 512 Stefano Stabellini
2009-05-21 12:08 ` Samuel Thibault
2009-05-21 13:17   ` Stefano Stabellini
2009-05-21 13:20     ` Samuel Thibault
2009-05-21 13:32       ` Keir Fraser
2009-05-22 14:31         ` Stefano Stabellini [this message]
2009-05-22 14:36           ` Samuel Thibault
2009-05-22 14:55             ` Stefano Stabellini

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=4A16B740.90809@eu.citrix.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=Keir.Fraser@eu.citrix.com \
    --cc=samuel.thibault@ens-lyon.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.