From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: John Mathew <john.mathew@unikie.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: complete_all() with x waiters in swake_up_all_locked
Date: Thu, 12 Dec 2019 18:12:30 +0100 [thread overview]
Message-ID: <20191212171230.ygveclhr5xqurys7@linutronix.de> (raw)
In-Reply-To: <CAJz2qXnHnw7Z9ftb6Oha5_0-R4YfUL+FhVZPNX1KKHyUkP6KNA@mail.gmail.com>
On 2019-12-11 09:17:49 [+0200], John Mathew wrote:
> Hi,
Hi,
> We are seeing the waring still appearing in the v5.0.3-rt1 tag of the
> rt linux kernel.
I didn't managed to reproduce it at the time. Now you say it works with
5.0-RT. I will try to give it a spin with the latest RT sometime next
week.
>
> Has there been any further investigation in to this warning following
> the previous discussion?
Thanks for report. I didn't manage to reproduce it so no. The actual
problem is that we are trying to figure out what a sane limit for
complete_all() might be. Most users of complete_all() have one two
waiters. Based on that report your max was 8 and that occurred a few
times.
> -John
Sebastian
next prev parent reply other threads:[~2019-12-12 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 7:17 complete_all() with x waiters in swake_up_all_locked John Mathew
2019-12-12 17:12 ` Sebastian Andrzej Siewior [this message]
2019-12-13 9:08 ` John Mathew
2019-12-18 16:53 ` Sebastian Andrzej Siewior
2019-12-31 10:00 ` [PATCH] crypto: only wait for completion once John Mathew
2020-01-14 12:47 ` Sebastian Andrzej Siewior
2020-02-11 11:48 ` John Mathew
2020-02-11 12:04 ` Sebastian Andrzej Siewior
2020-02-11 15:52 ` John Mathew
2020-02-11 15:59 ` Sebastian Andrzej Siewior
2020-02-12 12:55 ` John Mathew
2020-02-12 17:02 ` Sebastian Andrzej Siewior
2020-02-13 6:58 ` John Mathew
2020-02-13 8:31 ` Sebastian Andrzej Siewior
2020-02-18 7:18 ` [PATCH] swait: Increase number of waiters for warning John Mathew
2020-03-20 16:54 ` [PATCH RT] swait: Remove the warning with more than two waiters Sebastian Andrzej Siewior
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=20191212171230.ygveclhr5xqurys7@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=john.mathew@unikie.com \
--cc=linux-rt-users@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).