Date: Thu, 16 Jan 2014 14:28:42 -0800
From: Kent Overstreet <kmo@daterainc.com>
To: lsf-pc@lists.linux-foundation.org, LKML <linux-kernel@vger.kernel.org>,
        linux-fsdevel@vger.kernel.org
Subject: [LSF/MM TOPIC] [ATTEND] Direct IO
Message-ID: <20140116222842.GQ9037@kmo>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/