[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1427210823-5283-1-git-send-email-axboe@fb.com>
Date: Tue, 24 Mar 2015 09:26:57 -0600
From: Jens Axboe <axboe@...com>
To: <axboe@...nel.dk>, <linux-kernel@...r.kernel.org>,
<linux-fsdevel@...r.kernel.org>
CC: <ming.l@....samsung.com>
Subject: [PATCH RFC] Support for write stream IDs
Hi,
One of the things that exacerbates write amplification on flash
based devices is that fact that data with different lifetimes get
grouped together on media. Currently we have no interface that
applications can use to separate different types of writes. This
patch set adds support for that.
The kernel has no knowledge of what stream ID is what. The idea is
that writes with identical stream IDs have similar life times, not
that stream ID 'X' has a shorter lifetime than stream ID 'X+1'.
There are basically two interfaces that could be used for this. One
is fcntl, the other is fadvise. This patchset uses fadvise, with a
new POSIX_FADV_STREAMID hint. The 'offset' field is used to pass
the relevant stream ID. Switching to fcntl (with a SET/GET_STREAMID)
would be trivial.
The patchset wires up the block parts, adds buffered and O_DIRECT
support, and modifies btrfs/xfs too. It should be trivial to extend
this to all other file systems, I just used xfs and btrfs for testing.
No block drivers are wired up yet. Patches are against current -git.
block/bio.c | 2 ++
block/blk-core.c | 3 +++
fs/btrfs/inode.c | 1 +
fs/buffer.c | 4 ++--
fs/direct-io.c | 4 ++++
fs/fs-writeback.c | 1 +
fs/inode.c | 1 +
fs/mpage.c | 1 +
fs/open.c | 1 +
fs/xfs/xfs_aops.c | 1 +
include/linux/blk_types.h | 28 +++++++++++++++++++++++++++-
include/linux/fs.h | 11 +++++++++++
include/linux/writeback.h | 2 ++
include/uapi/linux/fadvise.h | 2 ++
mm/fadvise.c | 17 +++++++++++++++++
mm/filemap.c | 1 +
mm/migrate.c | 1 +
mm/page-writeback.c | 1 +
mm/vmscan.c | 1 +
19 files changed, 80 insertions(+), 3 deletions(-)
--
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/
Powered by blists - more mailing lists