linux-ext4 - Re: [patch 12/17] vfs: pagecache usage optimization for pagesize!=blocksize

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:	Mon, 28 Jul 2008 16:09:04 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	torvalds@...ux-foundation.org, hifumi.hisashi@....ntt.co.jp,
	hch@...radead.org, jack@....cz, linux-ext4@...r.kernel.org,
	nickpiggin@...oo.com.au
Subject: Re: [patch 12/17] vfs: pagecache usage optimization for
 pagesize!=blocksize

On Mon, 28 Jul 2008 19:00:32 -0400
Christoph Hellwig <hch@...radead.org> wrote:

> On Mon, Jul 28, 2008 at 03:46:36PM -0700, akpm@...ux-foundation.org wrote:
> > From: Hisashi Hifumi <hifumi.hisashi@....ntt.co.jp>
> > 
> > When we read some part of a file through pagecache, if there is a
> > pagecache of corresponding index but this page is not uptodate, read IO is
> > issued and this page will be uptodate.
> 
> I was under the impression we wanted to do this in a nicer way than 
> the hacky method?

The only description I've seen of "a nicer way" is vague two-word
descriptions of "changing readpage".  Or something.  No indication of
what those changes are, nor who will implement them nor when.

That just isn't solid enough to block a change which has significant
performance benefits.

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html