From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753477Ab1HGO1n (ORCPT ); Sun, 7 Aug 2011 10:27:43 -0400 Received: from mail-pz0-f42.google.com ([209.85.210.42]:62083 "EHLO mail-pz0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753016Ab1HGO1l (ORCPT ); Sun, 7 Aug 2011 10:27:41 -0400 Date: Sun, 7 Aug 2011 23:27:29 +0900 From: Minchan Kim To: Wu Fengguang Cc: Andrew Morton , Hugh Dickins , Matthew Wilcox , Linux Memory Management List , LKML Subject: Re: [PATCH] readahead: add comments on PG_readahead Message-ID: <20110807142729.GA2055@barrios-desktop> References: <20110805035040.GB11532@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110805035040.GB11532@localhost> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > CC: Matthew Wilcox > Signed-off-by: Wu Fengguang Reviewed-by: Minchan Kim I expect it would be very helpful. -- Kind regards, Minchan Kim