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]

Date:	Thu, 26 Apr 2007 00:22:42 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Nick Piggin <nickpiggin@...oo.com.au>
cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org, Mel Gorman <mel@...net.ie>,
	William Lee Irwin III <wli@...omorphy.com>,
	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, Nick Piggin wrote:

> > mapping through the radix tree. You just need to change the way the
> > filesystem looks up pages.
> 
> You didn't think any of the criticisms of higher order page cache size
> were valid?

They are all known points that have been discussed to death.

> > What are the exact requirement you are trying to address?
> 
> Block size > page cache size.

But what do you mean with it? A block is no longer a contiguous section of 
memory. So you have redefined the term.

> You guys have a couple of problems, firstly you need to have ia64
> filesystems accessable to x86_64. And secondly you have these controllers
> without enough sg entries for nice sized IOs.

This is not sgi specific sorry.

> I sympathise, and higher order pagecache might solve these in a way, but
> I don't think it is the right way to go, mainly because of the fragmentation
> issues.

And you dont care about Mel's work on that level?

> Increasing PAGE_SIZE, support for block size > page cache size, and getting
> io controllers matched to a 4K page size IMO would be some good ways to
> solve these problems. I know they are probably harder...

No this has been tried before and does not work. Why should we loose the 
capability to work with 4k pages just because there is some data that 
has to be thrown around in quantity? I'd like to have flexibility here.

The fragmentation problem is solvable and we already have a solution in 
mm. So I do not really see a problem there?
-
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/