linux-kernel - Re: [PATCH v9 6/6] block: loop: support DIO & AIO

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACVXFVMGt=46UL4FijvV7G_iqekDhmqWuXPLG1L8sBQhJ39EUg@mail.gmail.com>
Date:	Mon, 10 Aug 2015 10:33:04 -0400
From:	Ming Lei <ming.lei@...onical.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Dave Chinner <david@...morbit.com>, Jens Axboe <axboe@...nel.dk>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Kleikamp <dave.kleikamp@...cle.com>,
	Zach Brown <zab@...bo.net>,
	Maxim Patlasov <mpatlasov@...allels.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH v9 6/6] block: loop: support DIO & AIO

On Mon, Aug 10, 2015 at 4:08 AM, Christoph Hellwig <hch@...radead.org> wrote:
> 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.

Looks the default block size of mkfs.ext4/mkfs.xfs is 4096 for loop.

>
> 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.

IMO, using 4k sector size may not improve performance for most of
applications(buffered I/O, normal direct I/O) because the request from
these applications is already 4K aligned even the sector size is 512 and
the transfer from loop block device to backing file isn't changed basically.

Also for old applications, userpsace can't use 4K sector size.

BTW, could you let me know if you still object the approch(runtime switch)
in this patch? I am fine to not do that if you aren't happy with the approach.


Thanks,
Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/