Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 20 Jan 2002 16:19:41 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 20 Jan 2002 16:19:31 -0500 Received: from thebsh.namesys.com ([212.16.7.65]:21770 "HELO thebsh.namesys.com") by vger.kernel.org with SMTP id ; Sun, 20 Jan 2002 16:19:22 -0500 Message-ID: <3C4B3370.7020303@namesys.com> Date: Mon, 21 Jan 2002 00:15:28 +0300 From: Hans Reiser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011221 X-Accept-Language: en-us MIME-Version: 1.0 To: Rik van Riel CC: Shawn , linux-kernel@vger.kernel.org, Josh MacDonald Subject: Re: Possible Idea with filesystem buffering. In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Rik van Riel wrote: >On Sun, 20 Jan 2002, Hans Reiser wrote: > >>Write clustering is one thing it achieves. >> >>Flushing everything involved in a transaction ... is another thing. >> > >Agreed on these points, but you really HAVE TO work towards >flushing the page ->writepage() gets called for. > >Think about your typical PC, with memory in ZONE_DMA, >ZONE_NORMAL and ZONE_HIGHMEM. If we are short on DMA pages >we will end up calling ->writepage() on a DMA page. > >If the filesystem ends up writing completely unrelated pages >and marking the DMA page in question referenced the VM will >go in a loop until the filesystem finally gets around to >making a page in the (small) DMA zone freeable ... > This is a bug in VM design, yes? It should signal that it needs the particular page written, which probnably means that it should use writepage only when it needs that particular page written, and should otherwise check to see if the filesystem supports something like pressure_fs_cache(), yes? > > >regards, > >Rik > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/