[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1310012243220.5682@chino.kir.corp.google.com>
Date: Tue, 1 Oct 2013 22:47:36 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Bob Liu <lliubbo@...il.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
viro@...iv.linux.org.uk, mgorman@...e.de, hannes@...xchg.org,
riel@...hat.com, minchan@...nel.org, Bob Liu <bob.liu@...cle.com>
Subject: Re: [PATCH] mm: pagevec: cleanup: drop pvec->cold argument in all
places
On Mon, 30 Sep 2013, Andrew Morton wrote:
> > Nobody uses the pvec->cold argument of pagevec and it's also unreasonable for
> > pages in pagevec released as cold page, so drop the cold argument from pagevec.
>
> Is it unreasonable? I'd say it's unreasonable to assume that all pages
> in all cases are likely to be cache-hot. Example: what if the pages
> are being truncated and were found to be on the inactive LRU,
> unreferenced?
>
> A useful exercise would be to go through all those pagevec_init() sites
> and convince ourselves that the decision at each place was the correct
> one.
>
Agreed, and the "cold" argument to release_pages() becomes a no-op if this
patch is merged meaning that anything released through it will
automatically go to the start of the pcp lists. If the pages aren't hot
then this is exactly the opposite of what we wanted to do; the fact that
the pvec length doesn't take into account the size of cpu cache can almost
guarantee that everything isn't cache hot.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists