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.0704250818030.24363@schroedinger.engr.sgi.com>
Date:	Wed, 25 Apr 2007 08:23:11 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Mel Gorman <mel@...net.ie>
cc:	linux-kernel@...r.kernel.org,
	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 Wed, 25 Apr 2007, Mel Gorman wrote:

> HIGHMEM I can understand because I suppose the kmap() issue is still in
> there, but why 32 bit? Is this temporary or do you expect to see it
> fixed up later?

It could be fixed but I only tested with 64 bit. Jens's report shows that 
my skepticism was justified. 32 bit has only small memory and suffers from 
VM crappiness due to highmem, bouncing due to dma zones etc etc. Its a big 
mess that I would like to avoid dealing with for now. Lots of corner cases 
that need consideration. When we actually merge this then we can deal with 
all the cases. If some cases cannot be dealt with then the large blocksize 
support will not be available if another particular feature is 
enabled.

> >   How well Mel's antifrag/defrag methods address this issue still has to
> >   be seen.
> The grouping pages by mobility should hold up for ext2 and XFS because
> their page cache pages are reclaimable/movable and will get grouped with
> other pages that are reclaimable/movable. ramfs may be a problem if it was
> heavily used but lets see how things pan out.

Sounds good.
-
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/