From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Hannes Reinecke <hare@suse.de>, Jens Axboe <axboe@fb.com>,
Alexander Graf <agraf@suse.com>, Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] loop: enable different physical blocksizes
Date: Fri, 7 Aug 2015 09:33:30 +0200 [thread overview]
Message-ID: <20150807073330.GB17618@lst.de> (raw)
In-Reply-To: <CACVXFVP9T=JjQdf=DJ3vvkoOtByXka=zkuGkZi74-s2jmyG=gQ@mail.gmail.com>
On Mon, Jul 27, 2015 at 06:40:57AM -0400, Ming Lei wrote:
> On Fri, Jul 17, 2015 at 3:27 AM, Hannes Reinecke <hare@suse.de> wrote:
> > Currently the loop driver just simulates 512-byte blocks. When
> > creating images for virtual machines it might be required to use
> > a different physical blocksize (eg 4k for S/390 DASD).
>
> Looks 'qemu-img create' doesn't have parameter of block size,
> so could you share your use case? And I am just curious why
> 512-byte can't work for this case.
The use case is to suppot 4k sectors sizes such as DASDs usually provide,
or just to create a 4k block device to check your filesystem of choice
handles 4k sectors just fine. Replace 4k with other sector sizes of
your choice for added benefit. In addition to the DASD use case it's really a
very useful debugging tool.
next prev parent reply other threads:[~2015-08-07 7:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 7:27 [PATCH 0/4] loop: enable different physical blocksizes Hannes Reinecke
2015-07-17 7:27 ` [PATCH 1/4] loop: Enable correct physical blocksize Hannes Reinecke
2015-07-27 5:15 ` Christoph Hellwig
2015-07-27 5:59 ` Hannes Reinecke
2015-08-07 7:31 ` Christoph Hellwig
2015-07-17 7:27 ` [PATCH 2/4] loop: Remove unused 'bdev' argument from loop_set_capacity Hannes Reinecke
2015-07-27 5:16 ` Christoph Hellwig
2015-07-17 7:27 ` [PATCH 3/4] loop: Add 'lo_logical_blocksize' Hannes Reinecke
2015-07-17 7:27 ` [PATCH 4/4] loop: Pass logical blocksize in 'lo_init[0]' ioctl field Hannes Reinecke
2015-07-27 10:40 ` [PATCH 0/4] loop: enable different physical blocksizes Ming Lei
2015-08-03 23:00 ` Alexander Graf
2015-08-07 5:07 ` Ming Lei
2015-08-07 6:46 ` Hannes Reinecke
2015-08-07 7:23 ` Ming Lei
2015-08-07 7:45 ` Hannes Reinecke
2015-08-07 8:02 ` Ming Lei
2015-08-07 7:33 ` Christoph Hellwig [this message]
2015-08-07 7:44 ` Ming Lei
2015-08-07 7:48 ` Christoph Hellwig
2015-08-07 7:58 ` Ming Lei
2015-08-07 7:50 ` Hannes Reinecke
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=20150807073330.GB17618@lst.de \
--to=hch@lst.de \
--cc=agraf@suse.com \
--cc=axboe@fb.com \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tom.leiming@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox