linux-kernel - Re: [00/17] Large Blocksize Support 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]

Message-ID: <Pine.LNX.4.64.0704261115400.3263@schroedinger.engr.sgi.com>
Date:	Thu, 26 Apr 2007 11:16:17 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	William Lee Irwin III <wli@...omorphy.com>
cc:	Nick Piggin <nickpiggin@...oo.com.au>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org, Mel Gorman <mel@...net.ie>,
	David Chinner <dgc@....com>,
	Jens Axboe <jens.axboe@...cle.com>,
	Badari Pulavarty <pbadari@...il.com>,
	Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: [00/17] Large Blocksize Support V3

On Thu, 26 Apr 2007, William Lee Irwin III wrote:

> On Thu, Apr 26, 2007 at 05:42:17PM +1000, Nick Piggin wrote:
> > I don't think that it is solved, and I think the heuristics that are
> > there would be put under more stress if they become widely used. And
> > it isn't only about whether we can get the page or not, but also about
> > the cost. Look up Linus's arguments about page colouring, which are
> > similar and  I also think are pretty valid.
> 
> Perhaps broader exposure would help demonstrate their efficacy, or
> otherwise discover what deficits need to be addressed.

It would help if developers would once in a while look at how other 
operating systems handle this. They have supported such features for a 
long time.

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