From: Jason Low <jason.low2@hpe.com>
To: Waiman Long <waiman.long@hpe.com>
Cc: jason.low2@hpe.com, Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
imre.deak@intel.com, linux-kernel@vger.kernel.org,
Davidlohr Bueso <dave@stgolabs.net>,
Tim Chen <tim.c.chen@linux.intel.com>,
terry.rudd@hpe.com, "Paul E. McKenney" <paulmck@us.ibm.com>,
jason.low2@hp.com
Subject: Re: [PATCH v2] locking/mutex: Prevent lock starvation when spinning is enabled
Date: Tue, 16 Aug 2016 12:44:43 -0700 [thread overview]
Message-ID: <1471376683.17361.23.camel@j-VirtualBox> (raw)
In-Reply-To: <57AC9C64.7080500@hpe.com>
On Thu, 2016-08-11 at 11:40 -0400, Waiman Long wrote:
> On 08/10/2016 02:44 PM, Jason Low wrote:
> > +static inline void do_yield_to_waiter(struct mutex *lock, int *wakeups)
> > +{
> > + return;
> > +}
> > +
> > +static inline void clear_yield_to_waiter(struct mutex *lock)
> > +{
> > + return;
> > +}
> > +
> > +static inline bool need_yield_to_waiter(struct mutex *lock)
> > +{
> > + return false;
> > +}
> > +
> > #else
> > static bool mutex_optimistic_spin(struct mutex *lock,
> > struct ww_acquire_ctx *ww_ctx, const bool use_ww_ctx)
> > {
> > return false;
> > }
> > +
> > +#define MUTEX_WAKEUP_THRESHOLD 16
> > +
> > +static inline void do_yield_to_waiter(struct mutex *lock, int *wakeups)
> > +{
> > + *wakeups += 1;
> > +
> > + if (*wakeups< MUTEX_WAKEUP_THRESHOLD)
> > + return;
> > +
> > + if (lock->yield_to_waiter != true)
> > + lock->yield_to_waiter = true;
> > +}
> > +
> > +static inline void clear_yield_to_waiter(struct mutex *lock)
> > +{
> > + lock->yield_to_waiter = false;
> > +}
> > +
> > +static inline bool need_yield_to_waiter(struct mutex *lock)
> > +{
> > + return lock->yield_to_waiter;
> > +}
> > #endif
> >
> > _
>
> The *yield* helper functions should be in a separate conditional
> compilation block as the declaration of yield_to_waiter may not match
> the helper functions with certain combination of config variables.
>
> Something like
>
> #if !defined(CONFIG_MUTEX_SPIN_ON_OWNER) && defined(CONFIG_SMP)
> ...
> #else
> ...
> #endif
Right, we will need to incorporate the CONFIG_SMP logic when defining
these functions here, otherwise they would be undefined in the !SMP
case.
Thanks,
Jason
next prev parent reply other threads:[~2016-08-16 19:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 18:44 [PATCH v2] locking/mutex: Prevent lock starvation when spinning is enabled Jason Low
2016-08-10 20:00 ` kbuild test robot
2016-08-10 20:01 ` kbuild test robot
2016-08-16 20:19 ` Jason Low
2016-08-10 22:07 ` Jason Low
2016-08-11 2:30 ` Jason Low
2016-08-11 15:40 ` Waiman Long
2016-08-16 19:44 ` Jason Low [this message]
2016-08-17 1:41 ` Wanpeng Li
2016-08-17 18:30 ` Jason Low
2016-08-18 0:38 ` Wanpeng Li
2016-08-18 14:14 ` Peter Zijlstra
2016-08-18 15:22 ` Waiman Long
2016-08-18 14:27 ` Peter Zijlstra
2016-08-18 15:18 ` Peter Zijlstra
2016-08-18 15:30 ` Peter Zijlstra
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=1471376683.17361.23.camel@j-VirtualBox \
--to=jason.low2@hpe.com \
--cc=dave@stgolabs.net \
--cc=imre.deak@intel.com \
--cc=jason.low2@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@us.ibm.com \
--cc=peterz@infradead.org \
--cc=terry.rudd@hpe.com \
--cc=tim.c.chen@linux.intel.com \
--cc=waiman.long@hpe.com \
/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