linux-kernel - [LSF/MM TOPIC] [ATTEND] Direct IO

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20140116222842.GQ9037@kmo>
Date:	Thu, 16 Jan 2014 14:28:42 -0800
From:	Kent Overstreet <kmo@...erainc.com>
To:	lsf-pc@...ts.linux-foundation.org,
	LKML <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: [LSF/MM TOPIC] [ATTEND] Direct IO

Hi, I'd like to discuss the current state and future direction of the DIO code.

I and others have been kicking around the idea for some time now of reworking
direct IO at the filesystem level in terms of bios; this will radically simplify
fs/direct-IO.c, and solve some other longstanding issues, like double usage of
the page cache by the loopback device - the goal will be for things like loop to
just be able to submit bios to the filesystem code.

Immutable biovecs are now almost upstream, which was a major prereq; this helps
enables a DIO rewrite that basically pushes bios up a layer. Soon, we'll need to
start reworking vfs interfaces, and input from the filesystem developers
(especially btrfs) will be necessary there.
--
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/