From: Jens Axboe <axboe@kernel.dk>
To: Jan Kara <jack@suse.cz>, Kanchan Joshi <joshi.k@samsung.com>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
tytso@mit.edu, adilger.kernel@dilger.ca, jack@suse.com,
viro@zeniv.linux.org.uk, darrick.wong@oracle.com,
jrdr.linux@gmail.com, ebiggers@google.com,
jooyoung.hwang@samsung.com, chur.lee@samsung.com,
prakash.v@samsung.com
Subject: Re: [PATCH 2/2] fs/ext4,jbd2: Add support for passing write-hint with journal.
Date: Mon, 10 Dec 2018 08:17:18 -0700 [thread overview]
Message-ID: <9f693dd1-3c29-cdb4-90cd-83a27e21df4a@kernel.dk> (raw)
In-Reply-To: <20181210141226.GM29289@quack2.suse.cz>
On 12/10/18 7:12 AM, Jan Kara wrote:
> On Mon 10-12-18 18:20:04, Kanchan Joshi wrote:
>> This patch introduces "j_writehint" in JBD2 journal,
>> which is set based by Ext4 depending on "journal_writehint"
>> mount option (inspired from "journal_ioprio").
>
> Thanks for the patch! It would be good to provide the explanation you have
> in the cover letter in this patch as well so that it gets recorded in git
> logs.
>
> Also I don't like the fact that users have to set the hint via a mount
> option for this to be enabled. OTOH the WRITE_FILE_<foo> hints defined in
> fs.h are generally supposed to be used by userspace so it's difficult to
> pick anything if we don't know what the userspace is going to do. I'd argue
> it's even difficult for the sysadmin to pick any good value even if he
> actually knows that he might benefit from setting some. Jens, is there
> some reasonable way for fs to automatically pick some stream value for its
> journal?
I think we have two options here:
1) It's _probably_ safe to assume that journal data is short lived. While
hints are all relative to the specific use case, the size of the journal
compared to the rest of the drive is most likely very small. Hence a
default of WRITE_LIFE_SHORT is probably a good idea.
2) We add a specific internal life time hint for fs journals.
#2 makes the most sense to me, but requires a bit more work...
--
Jens Axboe
next prev parent reply other threads:[~2018-12-10 15:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20181210125245epcas2p202bc4336e91a55cee3786ed6abffea05@epcas2p2.samsung.com>
2018-12-10 12:50 ` [PATCH 0/2] fs,ext4,jbd2: Specifying write-hint for Ext4 journal Kanchan Joshi
[not found] ` <CGME20181210125251epcas1p3023db72cc08d6b2f899141d551d53f61@epcas1p3.samsung.com>
2018-12-10 12:50 ` [PATCH 1/2] fs: introduce APIs to enable sending write-hint with buffer-head Kanchan Joshi
2018-12-10 13:49 ` Jan Kara
2018-12-11 11:57 ` Kanchan Joshi
[not found] ` <CGME20181210125256epcas1p1e4142cfefb9b21dfb8dad927fbd49143@epcas1p1.samsung.com>
2018-12-10 12:50 ` [PATCH 2/2] fs/ext4,jbd2: Add support for passing write-hint with journal Kanchan Joshi
2018-12-10 14:12 ` Jan Kara
2018-12-10 15:17 ` Jens Axboe [this message]
2018-12-10 15:41 ` Jan Kara
2018-12-10 15:44 ` Jens Axboe
2018-12-11 4:07 ` Dave Chinner
2018-12-11 5:07 ` Jens Axboe
2018-12-11 13:53 ` Kanchan Joshi
2018-12-11 21:54 ` Dave Chinner
2018-12-12 22:21 ` Dave Chinner
2018-12-19 14:10 ` Kanchan Joshi
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=9f693dd1-3c29-cdb4-90cd-83a27e21df4a@kernel.dk \
--to=axboe@kernel.dk \
--cc=adilger.kernel@dilger.ca \
--cc=chur.lee@samsung.com \
--cc=darrick.wong@oracle.com \
--cc=ebiggers@google.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=jooyoung.hwang@samsung.com \
--cc=joshi.k@samsung.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=prakash.v@samsung.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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).