stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: significant drop fio IOPS performance on v5.10 #forregzbot
Date: Thu, 29 Sep 2022 07:36:20 -0400	[thread overview]
Message-ID: <YzWDNDw+++S+9272@mit.edu> (raw)
In-Reply-To: <9e3a4bf9-c909-d6aa-28c8-5fbbea9f5ae3@leemhuis.info>


This is a repeat of a discussion regarding changing the default of
dioread_nolock.  Note that you can "revert" this change in defaults by
using the mount options "nodioread_nolock" (or "dioread_lock").  There
were some good reasons why the change in the default was made, though.

#regzbot invalid: caused by a change of defaults that (among others) was
done for security reasons, see Ted's answer in
https://lore.kernel.org/all/Yypx6VQRbl3bFP2v@mit.edu/ for details

					- Ted

      reply	other threads:[~2022-09-29 11:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <357ace228adf4e859df5e9f3f4f18b49@amazon.com>
     [not found] ` <1cdc68e6a98d4e93a95be5d887bcc75d@amazon.com>
2022-09-28  6:07   ` significant drop fio IOPS performance on v5.10 Lu, Davina
2022-09-28 22:36     ` Theodore Ts'o
2022-10-05  7:24       ` Lu, Davina
2022-11-09  1:02       ` Lu, Davina
2022-09-29  7:03     ` significant drop fio IOPS performance on v5.10 #forregzbot Thorsten Leemhuis
2022-09-29 11:36       ` Theodore Ts'o [this message]

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=YzWDNDw+++S+9272@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /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).