From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S268860AbRHFVMv>; Mon, 6 Aug 2001 17:12:51 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S268952AbRHFVMk>; Mon, 6 Aug 2001 17:12:40 -0400
Received: from humbolt.nl.linux.org ([131.211.28.48]:48143 "EHLO
	humbolt.nl.linux.org") by vger.kernel.org with ESMTP
	id <S268860AbRHFVMd>; Mon, 6 Aug 2001 17:12:33 -0400
Content-Type: text/plain; charset=US-ASCII
From: Daniel Phillips <phillips@bonn-fries.net>
To: Chris Mason <mason@suse.com>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] using writepage to start io
Date: Mon, 6 Aug 2001 23:18:26 +0200
X-Mailer: KMail [version 1.2]
Cc: linux-mm@kvack.org
In-Reply-To: <755760000.997128720@tiny>
In-Reply-To: <755760000.997128720@tiny>
MIME-Version: 1.0
Message-Id: <01080623182601.01864@starship>
Content-Transfer-Encoding: 7BIT
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Monday 06 August 2001 22:12, Chris Mason wrote:
> On Monday, August 06, 2001 09:45:12 PM +0200 Daniel Phillips
>
> <phillips@bonn-fries.net> wrote:
> >> Almost ;-) memory pressure doesn't need to care about how long a
> >> buffer has been dirty, that's kupdate's job.  kupdate doesn't care
> >> if the buffer it is writing is a good candidate for freeing, that's
> >> taken care of elsewhere. The two never need to talk (aside from
> >> optimizations).
> >
> > My point is, they should talk, in fact they should be the same
> > function. It's never right for bdflush to submit younger buffers
> > when there are dirty buffers whose flush time has already passed.
>
> Grin, we're talking in circles.  My point is that by having two
> threads, bdflush is allowed to skip over older buffers in favor of
> younger ones because somebody else is responsible for writing the
> older ones out.

Yes, and you can't imagine an algorithm that could do that with *one* 
thread?

--
Daniel