From mboxrd@z Thu Jan 1 00:00:00 1970 From: William Lee Irwin III Subject: Re: Bufferheads & page-cache reference Date: Mon, 14 Feb 2005 14:50:33 -0800 Message-ID: <20050214225033.GY13009@holomorphy.com> References: <1108409415.20053.1278.camel@dyn318077bld.beaverton.ibm.com> <20050214134058.1402cfed.akpm@osdl.org> <20050214221044.GX13009@holomorphy.com> <20050214143142.6c12fdb3.akpm@osdl.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: pbadari@us.ibm.com, linux-fsdevel@vger.kernel.org, ext2-devel@lists.sourceforge.net Received: from holomorphy.com ([66.93.40.71]:26781 "EHLO holomorphy.com") by vger.kernel.org with ESMTP id S261475AbVBNWun (ORCPT ); Mon, 14 Feb 2005 17:50:43 -0500 To: Andrew Morton Content-Disposition: inline In-Reply-To: <20050214143142.6c12fdb3.akpm@osdl.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Feb 14, 2005 at 01:40:58PM -0800, Andrew Morton wrote: >>> Seems about right. There's also the buffer_heads_over_limit logic in >>> mm/vmscan.c and fs/buffer.c. That logic has a hole in that it requires >>> that there be a highmem shortage before we start to reclaim the lowmem >>> buffer_heads, but it is somewhat helpful. William Lee Irwin III wrote: >> It would be beneficial to close the hole in that logic. On Mon, Feb 14, 2005 at 02:31:42PM -0800, Andrew Morton wrote: > Really? Who's hurting? Apart from the fact that buffer_head proliferation has been a perennial problem, there's little to go on. By and large 2.6.x production usage is not yet very significant where I can see it, where the "production" usage is largely more stressful on account of very long durations and the variety of unusual situations to which the kernel is subjected. William Lee Irwin III wrote: >> Do you have any >> particularly preferred methods in mind? On Mon, Feb 14, 2005 at 02:31:42PM -0800, Andrew Morton wrote: > None that are particularly elegant. One approach might be to trigger a > highmem zone scan when we hit the limit, and to somehow tell that scan to > only do buffer_head stripping. This is largely what I expected. I'll cook something up depending on what conclusion is made from the above response. -- wli