linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: 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 12:22:09 -0400	[thread overview]
Message-ID: <53247E31.7060002@ubuntu.com> (raw)
In-Reply-To: <532417CA.1040300@gmail.com>

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


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

  parent reply	other threads:[~2014-03-15 16:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 15:54 Phillip Susi
2014-03-15  9:05 ` Michael Kerrisk (man-pages)
2014-03-15  9:24   ` Christoph Hellwig
2014-03-15 12:31     ` Michael Kerrisk (man-pages)
2014-03-15 16:22   ` Phillip Susi [this message]
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=53247E31.7060002@ubuntu.com \
    --to=psusi@ubuntu.com \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox