linux-kernel - writeback merge status, was Re: [PATCH 00/18] writeback fixes and cleanups for 2.6.40 (v3)

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:	Tue, 7 Jun 2011 08:13:36 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Wu Fengguang <fengguang.wu@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, Jan Kara <jack@...e.cz>,
	Dave Chinner <david@...morbit.com>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	torvalds@...ux-foundation.org
Subject: writeback merge status, was Re: [PATCH 00/18] writeback fixes and
 cleanups for 2.6.40 (v3)

It looks like we once again got no writeback fixes merged for $NEXT,
even with Wu having a very nice, well reviewed and tested series of 
fairly trivial patches.

I'm getting really frustrated about this.  We need a lot of work to
make writeback not suck with todays hardware and workloads, nevermind
tomorrows, and we're getting stalled for completely untransparent
reasons.  Basically people doing the work move ahead, then it gets stuck
in -mm which doesn't even get into linux-next and gets completely
stalled there.  So my vote is to have a proper peer-reviewed writeback
git tree, handled like all the other git trees we have, that is
maintained e.g. by Wu and make progress with that.

After fixing all those basic issues we have other big items like
I/O-less balance_dirty_pages and the memcg integration on our plate,
and with the current rate of progress we won't get there before Linux
4.0.

--
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/