linux-kernel - Re: [PATCH] VFS: Pagecache usage optimization on pagesize !=blocksize environment

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: <20080523225133.GB30591@atrey.karlin.mff.cuni.cz>
Date:	Sat, 24 May 2008 00:51:33 +0200
From:	Jan Kara <jack@...e.cz>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Hisashi Hifumi <hifumi.hisashi@....ntt.co.jp>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] VFS: Pagecache usage optimization on pagesize !=blocksize environment

> On Thu, 22 May 2008 16:31:15 +0900 Hisashi Hifumi <hifumi.hisashi@....ntt.co.jp> wrote:
> 
> One other thing we should think about here is the `nobh' mode which the
> extX filesystems support (although I have a feeling that Nick might
> have broken this ;)) We also have data=ordered, data=writeback and
> data=journal to think about.  This optimisation might not be
> appropriate at all to data=journal mode, but I haven't looked into
> that.
  Why do you think so? We mess with buffer_dirty bits in data=journal
mode but as far as I understand the patch, it only does not read the
page if the part we need is marked as uptodate in buffers. And this
should be safe.
  But I'm slightly confused that the patch helps because I've always
thought that mpage_readpage() (which is what we end up calling from
do_generic_mapping_read()) always reads the whole page. Thus either all
buffers in the page or none of them are uptodate... So what do I miss
here?

								Honza
-- 
Jan Kara <jack@...e.cz>
SuSE CR Labs
--
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/