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: <4631C674.9040506@yahoo.com.au>
Date:	Fri, 27 Apr 2007 19:46:28 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	William Lee Irwin III <wli@...omorphy.com>
CC:	David Chinner <dgc@....com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>, clameter@....com,
	linux-kernel@...r.kernel.org, Mel Gorman <mel@...net.ie>,
	Jens Axboe <jens.axboe@...cle.com>,
	Badari Pulavarty <pbadari@...il.com>,
	Maxim Levitsky <maximlevitsky@...il.com>
Subject: Re: [00/17] Large Blocksize Support V3

William Lee Irwin III wrote:
> On Fri, Apr 27, 2007 at 01:38:30AM +1000, Nick Piggin wrote:
> 
>>Or good grounds to increase the sg limit and push for io controller
>>manufacturers to do the same. If we have a hack in the kernel that
>>mostly works, they won't.
> 
> 
> On Fri, Apr 27, 2007 at 01:38:30AM +1000, Nick Piggin wrote:
> 
>>Page colouring was always rejected, and lots of people who knew
>>better got upset because it was the only way the hardware would go
>>fast...
> 
> 
> Yes, stunning wisdom there. Reject the speedups.

Yeah, that's how lots of people felt. But there is a good argument
to do just that.


> On Fri, Apr 27, 2007 at 01:38:30AM +1000, Nick Piggin wrote:
> 
>>You could put it that way. Or that it is wrong because of the
>>fragmenatation problem. Realise that it is somewhat fundamental
>>considering that it is basically an unsolvable problem with our
>>current kernel assumptions of unconstrained kernel allocations and
>>a 1:1 kernel mapping.
> 
> 
> Depends on what you consider a solution. A broadly used criterion is
> that improves performance significantly in important usage cases.

My criterion is that you are not suddenly unable to access your
filesystem because you cannot allocate a higher order page.

-- 
SUSE Labs, Novell Inc.
-
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/