Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 23 Jan 2002 18:52:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 23 Jan 2002 18:52:15 -0500 Received: from bay-bridge.veritas.com ([143.127.3.10]:28054 "EHLO svldns02.veritas.com") by vger.kernel.org with ESMTP id ; Wed, 23 Jan 2002 18:52:01 -0500 Date: Wed, 23 Jan 2002 23:53:35 +0000 (GMT) From: Hugh Dickins To: "Stephen C. Tweedie" cc: Rik van Riel , Andrew Morton , Hans Reiser , Andreas Dilger , Chris Mason , Shawn Starr , linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net Subject: Re: [Ext2-devel] Re: Possible Idea with filesystem buffering. In-Reply-To: <20020123203500.L1930@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 23 Jan 2002, Stephen C. Tweedie wrote: > > This is actually really important --- writepage on its own cannot > distinguish between requests to flush something to disk (eg. msync or > fsync), and requests to evict dirty data from memory. Actually, that much can now be distinguished: PageLaunder(page) when evicting from memory, !PageLaunder(page) when msync or fsync. Hugh - 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/