From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block: add logical_block_size property
Date: Mon, 3 May 2010 19:29:45 +0200 [thread overview]
Message-ID: <o2ifb8d4f71005031029la188a663ja7085b718e95d228@mail.gmail.com> (raw)
In-Reply-To: <20100304132017.GA2200@lst.de>
2010/3/4 Christoph Hellwig <hch@lst.de>:
>
> 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.
By "general" do you mean qemu, or the guests?
Solaris 2.0 - 2.5.1 and SunOS 4.x expect CDROM block size of 512 bytes.
Would have been nice to have the block size for CDROM configurable too.
Currently the CDROMs mentioned above have to be plugged as hard disks
in order to function.
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
prev parent reply other threads:[~2010-05-03 17:31 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 ` [Qemu-devel] " Christian Borntraeger
2010-03-17 15:59 ` [Qemu-devel] " Anthony Liguori
2010-05-03 17:29 ` Artyom Tarasenko [this message]
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=o2ifb8d4f71005031029la188a663ja7085b718e95d228@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=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).