From: Minchan Kim <minchan.kim@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Matthew Wilcox <willy@linux.intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] readahead: add comments on PG_readahead
Date: Sun, 7 Aug 2011 23:27:29 +0900 [thread overview]
Message-ID: <20110807142729.GA2055@barrios-desktop> (raw)
In-Reply-To: <20110805035040.GB11532@localhost>
On Fri, Aug 05, 2011 at 11:50:40AM +0800, Wu Fengguang wrote:
> Add comments to clarify the easily misunderstood PG_readahead timing.
>
> PG_readahead is a trigger to say, when you get this far, it's time to
> think about kicking off the _next_ readahead. -- Hugh
>
> CC: Hugh Dickins <hughd@google.com>
> CC: Matthew Wilcox <willy@linux.intel.com>
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
I expect it would be very helpful.
--
Kind regards,
Minchan Kim
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan.kim@gmail.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Matthew Wilcox <willy@linux.intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] readahead: add comments on PG_readahead
Date: Sun, 7 Aug 2011 23:27:29 +0900 [thread overview]
Message-ID: <20110807142729.GA2055@barrios-desktop> (raw)
In-Reply-To: <20110805035040.GB11532@localhost>
On Fri, Aug 05, 2011 at 11:50:40AM +0800, Wu Fengguang wrote:
> Add comments to clarify the easily misunderstood PG_readahead timing.
>
> PG_readahead is a trigger to say, when you get this far, it's time to
> think about kicking off the _next_ readahead. -- Hugh
>
> CC: Hugh Dickins <hughd@google.com>
> CC: Matthew Wilcox <willy@linux.intel.com>
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
I expect it would be very helpful.
--
Kind regards,
Minchan Kim
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-08-07 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 3:50 [PATCH] readahead: add comments on PG_readahead Wu Fengguang
2011-08-05 3:50 ` Wu Fengguang
2011-08-07 14:27 ` Minchan Kim [this message]
2011-08-07 14:27 ` Minchan Kim
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=20110807142729.GA2055@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@linux.intel.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.