From: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
To: Alexey Lyahkov <alexey.lyashkov@gmail.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>, Andreas Dilger <adilger@dilger.ca>,
Artem Blagodarenko <artem.blagodarenko@gmail.com>,
Andrew Perepechko <anserper@ya.ru>
Subject: Re: [PATCH] jbd2: wake up journal waiters in FIFO order, not LIFO
Date: Thu, 8 Sep 2022 11:41:53 +0530 [thread overview]
Message-ID: <20220908061153.dflgx7fjjav7pxyn@riteshh-domain> (raw)
In-Reply-To: <B32B956C-E851-42A2-9419-2947C442E2AA@gmail.com>
On 22/09/08 08:51AM, Alexey Lyahkov wrote:
> Hi Ritesh,
>
> This was hit on the Lustre OSS node when we have ton’s of short write with sync/(journal commit) in parallel.
> Each write was done from own thread (like 1k-2k threads in parallel).
> It caused a situation when only few/some threads make a wakeup and enter to the transaction until it will be T_LOCKED.
> In our’s observation all handles from head was waked and it’s handles added recently, while old handles still in list and
Thanks Alexey for providing the details.
> It caused a soft lockup messages on console.
Did you mean hung task timeout? I was wondering why will there be soft lockup
warning, because these old handles are anyway in a waiting state right.
Am I missing something?
-ritesh
next prev parent reply other threads:[~2022-09-08 6:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 16:59 [PATCH] jbd2: wake up journal waiters in FIFO order, not LIFO Alexey Lyashkov
2022-09-08 5:46 ` Ritesh Harjani (IBM)
2022-09-08 5:51 ` Alexey Lyahkov
2022-09-08 6:11 ` Ritesh Harjani (IBM) [this message]
2022-09-08 8:21 ` Alexey Lyahkov
2022-09-08 8:28 ` Andrew
2022-09-08 9:11 ` Ritesh Harjani (IBM)
2022-09-08 9:13 ` Ritesh Harjani (IBM)
-- strict thread matches above, loose matches on Subject: below --
2022-09-12 18:01 Alexey Lyashkov
2022-09-30 3:19 ` Theodore Ts'o
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=20220908061153.dflgx7fjjav7pxyn@riteshh-domain \
--to=ritesh.list@gmail.com \
--cc=adilger@dilger.ca \
--cc=alexey.lyashkov@gmail.com \
--cc=anserper@ya.ru \
--cc=artem.blagodarenko@gmail.com \
--cc=linux-ext4@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