From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] block: add logical_block_size property
Date: Wed, 17 Mar 2010 10:59:35 +0100 [thread overview]
Message-ID: <201003171059.35940.borntraeger@de.ibm.com> (raw)
In-Reply-To: <20100304132017.GA2200@lst.de>
Am Donnerstag 04 März 2010 14:20:17 schrieb Christoph Hellwig:
>
> Add a logical block size attribute as various guest side tools only
> increase the filesystem sector size based on it, not the advisory
> physical block size.
>
> For scsi we already have support for a different logical block size
> in place for CDROMs that we can built upon. Only my recent block
> device characteristics VPD page needs some fixups. Note that we
> leave the logial block size for CDROMs hardcoded as the 2k value
> is expected for it in general.
>
> For virtio-blk we already have a feature flag claiming to support
> a variable logical block size that was added for the s390 kuli
> hypervisor. Interestingly it does not actually change the units
> in which the protocol works, which is still fixed at 512 bytes,
> but only communicates a different minimum I/O granularity. So
> all we need to do in virtio is to add a trap for unaligned I/O
> and round down the device size to the next multiple of the logical
> block size.
>
> IDE does not support any other logical block size than 512 bytes.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Patch looks sane.
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
next prev parent reply other threads:[~2010-03-17 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 13:20 [Qemu-devel] [PATCH] block: add logical_block_size property Christoph Hellwig
2010-03-04 14:38 ` [Qemu-devel] " Christian Borntraeger
2010-03-05 9:26 ` [Qemu-devel] " Kevin Wolf
2010-03-05 9:32 ` Christoph Hellwig
2010-03-05 9:55 ` Kevin Wolf
2010-03-16 9:23 ` Christoph Hellwig
2010-03-17 9:59 ` Christian Borntraeger [this message]
2010-03-17 15:59 ` Anthony Liguori
2010-05-03 17:29 ` Artyom Tarasenko
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=201003171059.35940.borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=hch@lst.de \
--cc=qemu-devel@nongnu.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).