linux-kernel - Re: [RFC 1/7] cpuset write dirty map

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]

Message-Id: <20070627021408.493812fe.akpm@google.com>
Date:	Wed, 27 Jun 2007 02:14:08 -0700
From:	Andrew Morton <akpm@...gle.com>
To:	Christoph Lameter <clameter@....com>
Cc:	Ethan Solomita <solo@...gle.com>, linux-mm@...ck.org,
	LKML <linux-kernel@...r.kernel.org>, a.p.zijlstra@...llo.nl
Subject: Re: [RFC 1/7] cpuset write dirty map

On Tue, 26 Jun 2007 20:18:36 -0700 (PDT) Christoph Lameter <clameter@....com> wrote:

> On Tue, 26 Jun 2007, Andrew Morton wrote:
> 
> > Is in my queue somewhere.  Could be that by the time I get to it it will
> > need refreshing (again), we'll see.
> > 
> > One open question is the interaction between these changes and with Peter's
> > per-device-dirty-throttling changes.  They also are in my queue somewhere. 
> > Having a 100:1 coder:reviewer ratio doesn't exactly make for swift
> > progress.
> 
> Hmmmm.. How can we help? I can look at some aspects of Peter's per device 
> throttling.

That can't hurt.

I'm more concerned about all of Mel's code in -mm actually.  I don't recall
anyone doing a full review recently and I'm still not sure that this is the
overall direction in which we wish to go.  Last time I asked this everyone
seemed a bit waffly and non-committal.


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