From: Christoph Hellwig <hch@infradead.org>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: Phillip Susi <psusi@ubuntu.com>,
linux-man@vger.kernel.org, linux-mm@kvack.org,
linux-ext4@vger.kernel.org, Corrado Zoccolo <czoccolo@gmail.com>,
"Gregory P. Smith" <gps@google.com>,
Zhu Yanhai <zhu.yanhai@gmail.com>
Subject: Re: [PATCH] readahead.2: don't claim the call blocks until all data has been read
Date: Sat, 15 Mar 2014 02:24:55 -0700 [thread overview]
Message-ID: <20140315092455.GA6018@infradead.org> (raw)
In-Reply-To: <532417CA.1040300@gmail.com>
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.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-03-15 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 15:54 [PATCH] readahead.2: don't claim the call blocks until all data has been read Phillip Susi
[not found] ` <1394812471-9693-1-git-send-email-psusi-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
2014-03-15 9:05 ` Michael Kerrisk (man-pages)
2014-03-15 9:05 ` Michael Kerrisk (man-pages)
2014-03-15 9:24 ` Christoph Hellwig [this message]
2014-03-15 12:31 ` Michael Kerrisk (man-pages)
2014-03-15 12:31 ` Michael Kerrisk (man-pages)
[not found] ` <532417CA.1040300-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-03-15 16:22 ` Phillip Susi
2014-03-15 16:22 ` Phillip Susi
2014-03-15 16:25 ` Michael Kerrisk (man-pages)
2014-03-15 23:26 ` Phillip Susi
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=20140315092455.GA6018@infradead.org \
--to=hch@infradead.org \
--cc=czoccolo@gmail.com \
--cc=gps@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mtk.manpages@gmail.com \
--cc=psusi@ubuntu.com \
--cc=zhu.yanhai@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.