From: Kanchan Joshi <joshi.k@samsung.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-block@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-nvme@lists.infradead.org, jack@suse.com,
david@fromorbit.com, tytso@mit.edu, prakash.v@samsung.com,
Kanchan Joshi <joshi.k@samsung.com>
Subject: [PATCH v2 0/4] Write-hint for FS journal
Date: Wed, 09 Jan 2019 21:00:57 +0530 [thread overview]
Message-ID: <1547047861-7271-1-git-send-email-joshi.k@samsung.com> (raw)
In-Reply-To: CGME20190109153328epcas2p4643cbdc7a2182b47893a2bcaa0778e17@epcas2p4.samsung.com
Towards supporing write-hints/streams for filesystem journal.
Here is the v1 patch for background -
https://marc.info/?l=linux-fsdevel&m=154444637519020&w=2
Changes since v1:
- introduce four more hints for in-kernel use, as recommended by Dave chinner
& Jens axboe. This isolates kernel-mode hints from user-mode ones.
- remove mount-option to specify write-hint, as recommended by Jan kara &
Dave chinner. Rather, FS always sets write-hint for journal. This gets ignored
if device does not support stream.
- Removed code-redundancy for write_dirty_buffer (Jan kara's review comment)
Kanchan Joshi (4):
block: Increase count of supported write-hints
fs: introduce four macros for in-kernel hints
fs: introduce APIs to enable sending write-hint with buffer-head
fs/ext4,jbd2: add support for passing write-hint with journal.
fs/buffer.c | 18 ++++++++++++++++--
fs/ext4/super.c | 2 ++
fs/jbd2/commit.c | 11 +++++++----
fs/jbd2/journal.c | 3 ++-
fs/jbd2/revoke.c | 3 ++-
include/linux/blkdev.h | 5 ++++-
include/linux/buffer_head.h | 3 +++
include/linux/fs.h | 5 +++++
include/linux/jbd2.h | 8 ++++++++
9 files changed, 49 insertions(+), 9 deletions(-)
--
2.7.4
next parent reply other threads:[~2019-01-09 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20190109153328epcas2p4643cbdc7a2182b47893a2bcaa0778e17@epcas2p4.samsung.com>
2019-01-09 15:30 ` Kanchan Joshi [this message]
[not found] ` <CGME20190109153332epcas1p187b419176a8d1d0be4982a275c0b9e86@epcas1p1.samsung.com>
2019-01-09 15:30 ` [PATCH 1/4] block: Increase count of supported write-hints Kanchan Joshi
[not found] ` <CGME20190109153336epcas2p29b3275b6c545e483a3f43b92268f08bf@epcas2p2.samsung.com>
2019-01-09 15:30 ` [PATCH 2/4] fs: introduce four macros for in-kernel hints Kanchan Joshi
2019-01-23 18:27 ` [PATCH 2/4] " Javier González
2019-01-24 8:35 ` Jan Kara
2019-01-24 9:23 ` Javier González
[not found] ` <CGME20190109153339epcas2p4691a898dde0174a7565d62fcb3be0b6d@epcas2p4.samsung.com>
2019-01-09 15:31 ` [PATCH 3/4] fs: introduce APIs to enable sending write-hint with buffer-head Kanchan Joshi
[not found] ` <CGME20190109153342epcas2p3208f62a4dd876f8e1765b48f8aec2432@epcas2p3.samsung.com>
2019-01-09 15:31 ` [PATCH 4/4] fs/ext4,jbd2: add support for passing write-hint with journal Kanchan Joshi
2019-01-24 8:50 ` Jan Kara
2019-01-23 18:35 ` [PATCH v2 0/4] Write-hint for FS journal Javier González
2019-01-24 8:29 ` Jan Kara
2019-01-25 14:20 ` Kanchan Joshi
2019-01-25 16:23 ` Keith Busch
2019-01-28 12:47 ` Jan Kara
2019-01-28 23:24 ` Keith Busch
2019-01-29 10:07 ` Jan Kara
2019-01-30 0:13 ` Dave Chinner
2019-01-30 13:54 ` Kanchan Joshi
2019-02-05 11:50 ` Jan Kara
2019-02-05 22:53 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1547047861-7271-1-git-send-email-joshi.k@samsung.com \
--to=joshi.k@samsung.com \
--cc=david@fromorbit.com \
--cc=jack@suse.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=prakash.v@samsung.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).