From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Gregory Haskins <ghaskins@novell.com>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH] locking/rtmutex: Limit # of lock stealing for non-RT waiters
Date: Tue, 14 Jun 2022 11:06:17 -0400 [thread overview]
Message-ID: <34fea084-8136-5489-ef44-c5ecab51a86e@redhat.com> (raw)
In-Reply-To: <20220608152254.74591-1-longman@redhat.com>
On 6/8/22 11:22, Waiman Long wrote:
> Commit 48eb3f4fcfd3 ("locking/rtmutex: Implement equal priority lock
> stealing") allows unlimited number of lock stealing's for non-RT
> tasks. That can lead to lock starvation of non-RT top waiter if there
> is a constant incoming stream of non-RT lockers. This can cause task
> lockup in PREEMPT_RT kernel.
>
> Avoiding this problem and ensuring forward progress by limiting the
> number of times that a lock can be stolen from each waiter. This patch
> sets a threshold of 10. That number is arbitrary and can be changed
> if necessary.
>
> Fixes: 48eb3f4fcfd3 ("locking/rtmutex: Implement equal priority lock stealing")
> Signed-off-by: Waiman Long <longman@redhat.com>
Any comment on this patch?
Our QE team had verified that it fixed the lockup problem that they see
in our PREEMPT_RT kernel.
Thanks,
Longman
> ---
> kernel/locking/rtmutex.c | 9 ++++++---
> kernel/locking/rtmutex_common.h | 8 ++++++++
> 2 files changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
> index 7779ee8abc2a..bdddb3dc36c2 100644
> --- a/kernel/locking/rtmutex.c
> +++ b/kernel/locking/rtmutex.c
> @@ -359,10 +359,13 @@ static inline bool rt_mutex_steal(struct rt_mutex_waiter *waiter,
> if (rt_prio(waiter->prio) || dl_prio(waiter->prio))
> return false;
>
> - return rt_mutex_waiter_equal(waiter, top_waiter);
> -#else
> - return false;
> + if (rt_mutex_waiter_equal(waiter, top_waiter) &&
> + (top_waiter->nr_steals < RT_MUTEX_LOCK_STEAL_MAX)) {
> + top_waiter->nr_steals++;
> + return true;
> + }
> #endif
> + return false;
> }
>
> #define __node_2_waiter(node) \
> diff --git a/kernel/locking/rtmutex_common.h b/kernel/locking/rtmutex_common.h
> index c47e8361bfb5..5858efe5cb0e 100644
> --- a/kernel/locking/rtmutex_common.h
> +++ b/kernel/locking/rtmutex_common.h
> @@ -26,6 +26,7 @@
> * @task: task reference to the blocked task
> * @lock: Pointer to the rt_mutex on which the waiter blocks
> * @wake_state: Wakeup state to use (TASK_NORMAL or TASK_RTLOCK_WAIT)
> + * @nr_steals: Number of times the lock is stolen
> * @prio: Priority of the waiter
> * @deadline: Deadline of the waiter if applicable
> * @ww_ctx: WW context pointer
> @@ -36,11 +37,17 @@ struct rt_mutex_waiter {
> struct task_struct *task;
> struct rt_mutex_base *lock;
> unsigned int wake_state;
> + unsigned int nr_steals;
> int prio;
> u64 deadline;
> struct ww_acquire_ctx *ww_ctx;
> };
>
> +/*
> + * The maximum number of times where lock can be stolen per waiter.
> + */
> +#define RT_MUTEX_LOCK_STEAL_MAX 10
> +
> /**
> * rt_wake_q_head - Wrapper around regular wake_q_head to support
> * "sleeping" spinlocks on RT
> @@ -194,6 +201,7 @@ static inline void rt_mutex_init_waiter(struct rt_mutex_waiter *waiter)
> RB_CLEAR_NODE(&waiter->tree_entry);
> waiter->wake_state = TASK_NORMAL;
> waiter->task = NULL;
> + waiter->nr_steals = 0;
> }
>
> static inline void rt_mutex_init_rtlock_waiter(struct rt_mutex_waiter *waiter)
prev parent reply other threads:[~2022-06-14 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 15:22 Waiman Long
2022-06-14 15:06 ` Waiman Long [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=34fea084-8136-5489-ef44-c5ecab51a86e@redhat.com \
--to=longman@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=ghaskins@novell.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@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
all inboxes | Powered by JetHome®