linux-kernel - Re: [RFC PATCH 00/22] loop: Issue O

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: <4F4C036A.2080808@zabbo.net>
Date:	Mon, 27 Feb 2012 17:27:54 -0500
From:	Zach Brown <zab@...bo.net>
To:	Dave Kleikamp <dave.kleikamp@...cle.com>
CC:	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 00/22] loop: Issue O_DIRECT aio with pages

On 02/27/2012 04:19 PM, Dave Kleikamp wrote:
> This patchset was begun by Zach Brown and was originally submitted for
> review in October, 2009.

Man, it's been a while.  I remembered almost none of the details of this
work when I read your introductory message.  As I read the patches it
all came flooding back, though.  Yikes :).

My biggest fear about this patch series is the sheer amount of very
fiddly code motion.  I remember spending a lot of time verifying that
the patches didn't accidentally lose new changes as the patches were
ported to newer kernels.

Has someone gone through these most recent patches with an absurdly fine
toothed comb?  The patches that touch fs/direct-io.c and mm/filemap.c
are the most risky, by far.

> This series was written to reduce the current overhead loop imposes by
> performing synchronus buffered file system IO from a kernel thread.  These
> patches turn loop into a light weight layer that translates bios into iocbs.

It'd be worth including some simple benchmark results, I think.  I
remember testing with concurrent O_DIRECT aio with fio on a loopback
device on top of files in each underlying file system.

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