From: hazem ahmed mohamed <hazem.ahmed.abuelfotoh@gmail.com>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
"tytso@mit.edu" <tytso@mit.edu>,
"adilger.kernel@dilger.ca" <adilger.kernel@dilger.ca>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>
Subject: Re: Ext4: Buffered random writes performance regression with dioread_nolock enabled
Date: Wed, 21 Sep 2022 13:22:55 +0100 [thread overview]
Message-ID: <CACX6voCxHGd46ehrsys+3sVrA2Stq++O2ofh7E6f4MTN59Z2NQ@mail.gmail.com> (raw)
In-Reply-To: <20220921044419.epojssm3g4j3qkup@riteshh-domain>
Thanks for sharing that unfortunately this patch has been merged to
kernel 5.7 and I am still seeing that regression with later versions
that include that patch.
Hazem.
On Wed, 21 Sept 2022 at 05:44, Ritesh Harjani (IBM)
<ritesh.list@gmail.com> wrote:
>
> On 22/09/19 04:18PM, hazem ahmed mohamed wrote:
> > Hey Team,
> >
> >
> >
> > I am sending this e-mail to report a performance regression that’s
> > caused by commit 244adf6426(ext4: make dioread_nolock the default) , I
> > am listing the performance regression symptoms below & our analysis
> > for the reported regression.
> >
>
> Although you did mention you already tested on the latest kernel too and there
> too you saw a similar performance regression.
> But no harm in also double checking if you have this patch [1].
> This does fixes a similar problem AFAIU.
>
>
> [1]: https://lore.kernel.org/linux-ext4/20200520133119.1383-1-jack@suse.cz/
>
> -ritesh
next prev parent reply other threads:[~2022-09-21 12:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 15:18 Ext4: Buffered random writes performance regression with dioread_nolock enabled hazem ahmed mohamed
2022-09-20 8:07 ` Thorsten Leemhuis
2022-09-20 13:59 ` hazem ahmed mohamed
2022-09-21 2:41 ` Theodore Ts'o
2022-09-21 9:55 ` Thorsten Leemhuis
2022-09-21 4:44 ` Ritesh Harjani (IBM)
2022-09-21 12:22 ` hazem ahmed mohamed [this message]
[not found] <28460B7B-F66E-4BDC-9F6E-B7E77A3FEE83@amazon.com>
2022-09-21 2:07 ` Theodore Ts'o
2022-09-21 12:06 ` Mohamed Abuelfotoh, Hazem
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=CACX6voCxHGd46ehrsys+3sVrA2Stq++O2ofh7E6f4MTN59Z2NQ@mail.gmail.com \
--to=hazem.ahmed.abuelfotoh@gmail.com \
--cc=abuehaze@amazon.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=ritesh.list@gmail.com \
--cc=stable@vger.kernel.org \
--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