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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <46304C74.9040304@yahoo.com.au>
Date:	Thu, 26 Apr 2007 16:53:40 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	Christoph Lameter <clameter@....com>
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

Christoph Lameter wrote:
> On Thu, 26 Apr 2007, Nick Piggin wrote:
> 
> 
>>>The page cache has no problems supporting things with a block
>>>size larger then page size.  Now the block device layer may not
>>>have the code to do the scatter gather into small pages and it
>>>may not handle buffer heads whose data is split between multiple
>>>pages. 
>>
>>Yeah, this patch is not really large blocksize support (which we normally
>>think of as block size > page cache size).
> 
> 
> No? It depends on how you define block size. This patch definitely allows
> a set blocksize function call with a size larger than 4k.

Yeah because it is still <= page cache page size. Anyway, that's just
semantics, it doesn't matter.


>>>I suspect what needs to be fixed is the page cache block device
>>>interface so that we have helper functions that know how to stuff
>>>a single block into several pages.
>>
>>I am working now and again on some code to do this, it is a big job but
>>I think it is the right way to do it. But it would take a long time to
>>get stable and supported by filesystems...
> 
> 
> Ummm... We already have a radix tree for this???? What more is needed? You 
> just need to go through all filesystems and make them use extends.

I'm talking about block size > page size in the buffer layer.

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