From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@canonical.com>
Cc: Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Kleikamp <dave.kleikamp@oracle.com>,
Zach Brown <zab@zabbo.net>,
Maxim Patlasov <mpatlasov@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH v9 6/6] block: loop: support DIO & AIO
Date: Mon, 10 Aug 2015 01:08:40 -0700 [thread overview]
Message-ID: <20150810080840.GA2293@infradead.org> (raw)
In-Reply-To: <CACVXFVMBqNQAb6iCm8TOWDyFmgPnjvACFJ9wvWEeCaKiZAB22g@mail.gmail.com>
On Sun, Aug 09, 2015 at 10:50:41PM -0400, Ming Lei wrote:
> Christoph, could you share your idea again about this approch?
>
> If you still don't think it is good to switch between buffered I/O
> and direct I/O, I will not do that in next post.
If we epxose a 512 byte block size to the loop device people will use
it, for example mkfs.xfs might do smaller I/O, extN will default to
small blocksize for small devices, etc.
If you are using a loop devices on a 4k sector backing device and care
about performance (which current loop users generally don't..) just
make sure to set the loop block size to 4k, which Hannes' series will
allow us to do easily.
next prev parent reply other threads:[~2015-08-10 8:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 8:42 [PATCH v9 0/6] block: loop: improve loop with AIO Ming Lei
2015-08-06 8:42 ` [PATCH v9 1/6] fs: direct-io: don't dirtying pages for ITER_BVEC/ITER_KVEC direct read Ming Lei
2015-08-06 8:42 ` [PATCH v9 2/6] block: loop: set QUEUE_FLAG_NOMERGES for request queue of loop Ming Lei
2015-08-06 8:42 ` [PATCH v9 3/6] block: loop: use kthread_work Ming Lei
2015-08-06 8:42 ` [PATCH v9 4/6] block: loop: prepare for supporing direct IO Ming Lei
2015-08-06 8:42 ` [PATCH v9 5/6] block: loop: introduce ioctl command of LOOP_SET_DIRECT_IO Ming Lei
2015-08-06 8:42 ` [PATCH v9 6/6] block: loop: support DIO & AIO Ming Lei
2015-08-07 7:43 ` Christoph Hellwig
2015-08-07 8:25 ` Ming Lei
2015-08-09 6:44 ` Christoph Hellwig
2015-08-09 13:04 ` Ming Lei
2015-08-09 13:44 ` Christoph Hellwig
2015-08-09 14:27 ` Ming Lei
2015-08-09 23:41 ` Dave Chinner
2015-08-10 2:50 ` Ming Lei
2015-08-10 8:08 ` Christoph Hellwig [this message]
2015-08-10 14:33 ` Ming Lei
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=20150810080840.GA2293@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dave.kleikamp@oracle.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=mpatlasov@parallels.com \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zab@zabbo.net \
/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