public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [PATCH v2] virtio_blk: check for hardsector size from host
Date: Fri, 30 May 2008 13:41:45 +1000	[thread overview]
Message-ID: <200805301341.46175.rusty@rustcorp.com.au> (raw)
In-Reply-To: <200805291108.26375.borntraeger@de.ibm.com>

On Thursday 29 May 2008 19:08:26 Christian Borntraeger wrote:
> Currently virtio_blk assumes a 512 byte hard sector size. This can cause
> trouble / performance issues if the backing has a different block size
> (like a file on an ext3 file system formatted with 4k block size or a
> dasd).
>
> Lets add a feature flag that tells the guest to use a different hard sector
> size than 512 byte.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>

Thanks.  I've queued this for next kernel (the other two will go 
striaght-away).

Cheers,
Rusty.

      reply	other threads:[~2008-05-30  3:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27  9:04 [PATCH/RFC] virtio_blk: check for hardsector size from host Christian Borntraeger
2008-05-29  8:04 ` Rusty Russell
2008-05-29  8:11   ` Christian Borntraeger
2008-05-29  8:12   ` Jens Axboe
2008-05-29  8:13     ` Jens Axboe
2008-05-29  8:27       ` Christian Borntraeger
2008-05-29  8:30         ` Jens Axboe
2008-05-29  9:08           ` [PATCH] virtio_config: fix len calculation of config elements Christian Borntraeger
2008-05-30  3:18             ` Rusty Russell
2008-05-29  9:08           ` [PATCH v2] virtio_blk: check for hardsector size from host Christian Borntraeger
2008-05-30  3:41             ` Rusty Russell [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=200805301341.46175.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=borntraeger@de.ibm.com \
    --cc=jens.axboe@oracle.com \
    --cc=kvm@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox