From: Jan Kara <jack@suse.cz>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>, Ritesh Harjani <riteshh@linux.ibm.com>,
Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
joseph.qi@linux.alibaba.com, Liu Bo <bo.liu@linux.alibaba.com>
Subject: Re: Discussion: is it time to remove dioread_nolock?
Date: Tue, 7 Jan 2020 18:22:36 +0100 [thread overview]
Message-ID: <20200107172236.GJ25547@quack2.suse.cz> (raw)
In-Reply-To: <20200107171109.GB3619@mit.edu>
On Tue 07-01-20 12:11:09, Theodore Y. Ts'o wrote:
> Hmm..... There's actually an even more radical option we could use,
> given that Ritesh has made dioread_nolock work on block sizes < page
> size. We could make dioread_nolock the default, until we can revamp
> ext4_writepages() to write the data blocks first....
Yes, that's a good point. And I'm not opposed to that if it makes the life
simpler. But I'd like to see some performance numbers showing how much is
writeback using unwritten extents slower so that we don't introduce too big
regression with this...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2020-01-07 17:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-26 15:31 Discussion: is it time to remove dioread_nolock? Theodore Y. Ts'o
2019-12-27 13:10 ` Joseph Qi
2019-12-29 15:03 ` Xiaoguang Wang
2020-01-06 12:24 ` Ritesh Harjani
2020-01-07 0:43 ` Theodore Y. Ts'o
2020-01-07 8:22 ` Jan Kara
2020-01-07 17:11 ` Theodore Y. Ts'o
2020-01-07 17:22 ` Jan Kara [this message]
2020-01-08 10:45 ` Ritesh Harjani
2020-01-08 17:42 ` Theodore Y. Ts'o
2020-01-09 9:21 ` Ritesh Harjani
2020-01-09 16:38 ` Theodore Y. Ts'o
2020-01-14 23:30 ` Ritesh Harjani
2020-01-15 16:48 ` Theodore Y. Ts'o
2020-01-16 9:46 ` Ritesh Harjani
2020-01-09 12:34 ` Jan Kara
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=20200107172236.GJ25547@quack2.suse.cz \
--to=jack@suse.cz \
--cc=bo.liu@linux.alibaba.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=tytso@mit.edu \
--cc=xiaoguang.wang@linux.alibaba.com \
/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).