From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: disable mount with both dioread_nolock and nodelalloc
Date: Sat, 7 Sep 2019 12:00:04 -0400 [thread overview]
Message-ID: <20190907160004.GB23683@mit.edu> (raw)
In-Reply-To: <20190731130600.7867-1-xiaoguang.wang@linux.alibaba.com>
On Wed, Jul 31, 2019 at 09:06:00PM +0800, Xiaoguang Wang wrote:
> Mount with both dioread_nolock and nodelalloc will result in huge
> performance drop, which indeed is an known issue, so before we fix
> this issue, currently we disable this behaviour. Below test reproducer
> can reveal this performance drop.
Is it really worth it to disable this combination? Nothing goes
*wrong* per se; it's just slower than we would like.
- Ted
next prev parent reply other threads:[~2019-09-08 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 13:06 [PATCH] ext4: disable mount with both dioread_nolock and nodelalloc Xiaoguang Wang
2019-08-01 1:57 ` Joseph Qi
2019-09-02 1:31 ` Xiaoguang Wang
2019-09-07 16:00 ` Theodore Y. Ts'o [this message]
2019-09-09 3:40 ` Xiaoguang Wang
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=20190907160004.GB23683@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--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).