linux-kernel - Re: [PATCH 0/3] implement readpages() for block device to optimize sequential read

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAC5umygJozyMs5ybyDjCeZLrPnJOAYoNnjsvAFkYFRfVZiivKQ@mail.gmail.com>
Date:	Sat, 16 Aug 2014 02:09:44 +0900
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>, Jens Axboe <axboe@...nel.dk>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Jeff Moyer <jmoyer@...hat.com>, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/3] implement readpages() for block device to optimize
 sequential read

2014-08-15 7:04 GMT+09:00 Andrew Morton <akpm@...ux-foundation.org>:
> On Tue,  5 Aug 2014 23:38:31 +0900 Akinobu Mita <akinobu.mita@...il.com> wrote:
>
>> This patchset implements readpages() operation for block device by
>> using mpage_readpages() which can create multipage BIOs instead of
>> BIOs for each page and reduce system CPU time consumption.
>
> Patchset is simple and straightforward enough.  But who the
> heck cares about the performance of buffered reads from /dev/XXX?

I tend to consider the block device as a baseline when I measure the
performance of the storage device.  So I was a bit surprised when I saw
the performance of buffered reads from filesystem is better than the one
from block device.  That is the reason about this patch for me.
--
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/