linux-kernel - Re: [PATCH 0/7] Per-bdi writeback flusher threads v20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 11 Sep 2009 22:39:29 +0800
From:	Wu Fengguang <fengguang.wu@...el.com>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Theodore Tso <tytso@....edu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	"chris.mason@...cle.com" <chris.mason@...cle.com>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
	"jack@...e.cz" <jack@...e.cz>
Subject: Re: [PATCH 0/7] Per-bdi writeback flusher threads v20

On Fri, Sep 11, 2009 at 10:29:26PM +0800, Jens Axboe wrote:
> On Fri, Sep 11 2009, Christoph Hellwig wrote:
> > 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.
> 
> I'd also appreciate if we can keep Wu (or Ted's) patch out of the merge
> until after -rc1 or at least with a few -git releases in between, so
> it'll be easier to check for regressions.

That would be good. Sorry for the late work. I'll allocate some time
in mid next week to help review and benchmark recent writeback works,
and hope to get things done in this merge window.

Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/