From: Jamie Lokier <jamie@shareable.org>
To: Avi Kivity <avi@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] Re: [PATCH v2] virtio-blk physical block size
Date: Tue, 5 Jan 2010 20:18:01 +0000 [thread overview]
Message-ID: <20100105201801.GK14376@shareable.org> (raw)
In-Reply-To: <4B4192A1.3030801@redhat.com>
Avi Kivity wrote:
> Physical block size is the what the logical block size would have been
> is software didn't suck. In theory they should be the same, but since
> compatibility reaons clamp the logical block size to 512, they have to
> differ. A disk may have a physical block size of 4096 and emulate
> logical block size of 512 on top of that using read-modify-write.
>
> Or so I understand it.
I think that's right, but a side effect is that if you get a power
failure during the read-modify-write, bytes anywhere in 4096 sector
may be incorrect, so journalling (etc.) needs to use 4096 byte blocks
for data integrity, even though the drive emulates smaller writes.
-- Jamie
next prev parent reply other threads:[~2010-01-05 20:18 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 16:39 [PATCH v2] virtio-blk physical block size Avi Kivity
2010-01-04 3:08 ` Rusty Russell
2010-01-04 3:08 ` [Qemu-devel] " Rusty Russell
2010-01-04 7:02 ` Avi Kivity
2010-01-04 7:02 ` Avi Kivity
2010-01-04 7:02 ` [Qemu-devel] " Avi Kivity
2010-01-05 20:18 ` Jamie Lokier
2010-01-05 20:18 ` Jamie Lokier [this message]
2010-01-04 8:30 ` Christoph Hellwig
2010-01-04 8:30 ` Christoph Hellwig
2010-01-04 8:30 ` Christoph Hellwig
2010-01-05 12:56 ` Rusty Russell
2010-01-05 12:56 ` Rusty Russell
2010-01-05 12:58 ` Avi Kivity
2010-01-05 12:58 ` Avi Kivity
2010-01-05 20:16 ` Jamie Lokier
2010-01-05 20:16 ` Jamie Lokier
2010-01-08 15:40 ` Christoph Hellwig
2010-01-08 15:40 ` Christoph Hellwig
2010-01-10 12:35 ` Avi Kivity
2010-01-10 12:35 ` Avi Kivity
2010-01-10 12:35 ` Avi Kivity
2010-01-08 15:40 ` Christoph Hellwig
2010-01-05 20:16 ` Jamie Lokier
2010-01-05 12:58 ` Avi Kivity
2010-01-05 12:56 ` Rusty Russell
2010-01-04 3:08 ` Rusty Russell
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=20100105201801.GK14376@shareable.org \
--to=jamie@shareable.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.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 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.