linux-ext4 - [RFC PATCH 0/4] ext4: implement DIO read nolocking

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>] [day] [month] [year] [list]

Message-ID: <5df78e1d0912151736xa1107afrdc5a343ee0f5e0d@mail.gmail.com>
Date:	Tue, 15 Dec 2009 17:36:23 -0800
From:	Jiaying Zhang <jiayingz@...gle.com>
To:	ext4 development <linux-ext4@...r.kernel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Michael Rubin <mrubin@...gle.com>
Subject: [RFC PATCH 0/4] ext4: implement DIO read nolocking

Hi all,

Several weeks ago, we proposed the idea of always allocating uninitialized
extent during ext4 DIO write and/or buffer write and convert the extent into
initialized after IO complete. This allows us to drop the i_mutex lock during
ext4 DIO read, which would help improve ext4 DIO read performance with
multiple threads or AIOs running on high-speed SSDs. FYI, here is the email
thread referred to: http://marc.info/?l=linux-ext4&m=125513220225086&w=2

Following this email are our RFC patches to implement the proposed idea.
We haven't tested these patches much so they are probably very buggy.

Any feedback would be greatly appreciated!

Regards,

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