linux-ext4 - Re: [PATCH] readahead.2: don't claim the call blocks until all data has been 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]

Date:	Sat, 15 Mar 2014 17:25:35 +0100
From:	"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To:	Phillip Susi <psusi@...ntu.com>
Cc:	linux-man <linux-man@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	linux-ext4@...r.kernel.org, Corrado Zoccolo <czoccolo@...il.com>,
	"Gregory P. Smith" <gps@...gle.com>,
	Zhu Yanhai <zhu.yanhai@...il.com>
Subject: Re: [PATCH] readahead.2: don't claim the call blocks until all data
 has been read

On Sat, Mar 15, 2014 at 5:22 PM, Phillip Susi <psusi@...ntu.com> wrote:
> On 03/15/2014 05:05 AM, Michael Kerrisk (man-pages) wrote:
>>
>> I've tweaked your text a bit to make some details clearer (I hope):
>>
>>         readahead()  initiates  readahead  on a file so that subsequent
>>         reads from that file will, be satisfied from the cache, and not
>>         block  on  disk I/O (assuming the readahead was initiated early
>>         enough and that other activity on the system  did  not  in  the
>>         meantime flush pages from the cache).
>
>
> Slight grammatical error there: there's an extra comma in "file will, be".

Thanks. Fixed.

Otherwise okay, I assume?
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html