Date: Fri, 11 Sep 2009 10:16:59 -0400
From: Christoph Hellwig <hch@infradead.org>
To: Theodore Tso <tytso@mit.edu>, Jens Axboe <jens.axboe@oracle.com>,
       linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
       chris.mason@oracle.com, hch@infradead.org, akpm@linux-foundation.org,
       jack@suse.cz, Wu Fengguang <fengguang.wu@intel.com>
Subject: Re: [PATCH 0/7] Per-bdi writeback flusher threads v20
Message-ID: <20090911141659.GA3508@infradead.org>
References: <1252654450-25721-1-git-send-email-jens.axboe@oracle.com> <20090911134241.GB19707@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090911134241.GB19707@mit.edu>
User-Agent: Mutt/1.5.19 (2009-01-05)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1201
Lines: 25

On Fri, Sep 11, 2009 at 09:42:41AM -0400, Theodore Tso wrote:
> > v19 include:
> > 
> > - Drop the max writeback pages patch from Ted. I think we should do
> >   something to that effect, but there's really no reason to entangle
> >   it with this patchset.
> 
> That's reasonable, but I'd really like to know whether some VM hacker
> going to try to deal with this during the 2.6.32 window?  Such as
> maybe Wu Fengguang's patches, perhaps?  
> 
> Or do I need to put in some kind of hack into ext4 ala what XFS did to
> work around this problem until we can come up with a longer-term fix?

I defintively want to see something in the VM, but I also agree with
Jens' decision not to include it in the patchkit.  It's not really
related to the patchkit except for depending on it, and we still
have a lot of discussion going on.  If we can't get an agreement with
the VM people by the end of the regular merge window I'm all for pushing
your simple patch.
--
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/