[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKgNAkgGZ-3U8PLKrZZ5KUWMmopd1B777_6ekva5ZpeXecEZ1g@mail.gmail.com>
Date: Sat, 15 Mar 2014 13:31:02 +0100
From: "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Phillip Susi <psusi@...ntu.com>,
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 10:24 AM, Christoph Hellwig <hch@...radead.org> wrote:
> On Sat, Mar 15, 2014 at 10:05:14AM +0100, Michael Kerrisk (man-pages) wrote:
>> However, it may block while it reads
>> the filesystem metadata needed to locate the requested blocks.
>> This occurs frequently with ext[234] on large files using indi???
>> rect blocks instead of extents, giving the appearence that the
>> call blocks until the requested data has been read.
>>
>> Okay?
>
> The part above is something that should be in the BUGS section.
Good call. Done. Thanks, Christoph.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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
Powered by blists - more mailing lists