From: Peter Zijlstra <peterz@infradead.org>
To: Alex Kogan <alex.kogan@oracle.com>
Cc: linux@armlinux.org.uk, mingo@redhat.com, will.deacon@arm.com,
arnd@arndb.de, longman@redhat.com, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, steven.sistare@oracle.com,
daniel.m.jordan@oracle.com, dave.dice@oracle.com,
rahul.x.yadav@oracle.com, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 3/3] locking/qspinlock: Introduce starvation avoidance into CNA
Date: Thu, 31 Jan 2019 11:00:09 +0100 [thread overview]
Message-ID: <20190131100009.GB31534@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190131030136.56999-4-alex.kogan@oracle.com>
On Wed, Jan 30, 2019 at 10:01:35PM -0500, Alex Kogan wrote:
> Choose the next lock holder among spinning threads running on the same
> socket with high probability rather than always. With small probability,
> hand the lock to the first thread in the secondary queue or, if that
> queue is empty, to the immediate successor of the current lock holder
> in the main queue. Thus, assuming no failures while threads hold the
> lock, every thread would be able to acquire the lock after a bounded
> number of lock transitions, with high probability.
>
> Note that we could make the inter-socket transition deterministic,
> by sticking a counter of intra-socket transitions in the head node
> of the secondary queue. At the handoff time, we could increment
> the counter and check if it is below a threshold. This adds another
> field to queue nodes and nearly-certain local cache miss to read and
> update this counter during the handoff. While still beating stock,
> this variant adds certain overhead over the probabilistic variant.
(also heavily suffers from the socket == node confusion)
How would you suggest RT 'tunes' this?
RT relies on FIFO fairness of the basic spinlock primitives; you just
completely wrecked that.
next prev parent reply other threads:[~2019-01-31 10:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 3:01 [PATCH 0/3] Add NUMA-awareness to qspinlock Alex Kogan
2019-01-31 3:01 ` Alex Kogan
2019-01-31 3:01 ` [PATCH 1/3] locking/qspinlock: Make arch_mcs_spin_unlock_contended more generic Alex Kogan
2019-01-31 3:01 ` Alex Kogan
2019-01-31 3:01 ` [PATCH 2/3] locking/qspinlock: Introduce CNA into the slow path of qspinlock Alex Kogan
2019-01-31 3:01 ` Alex Kogan
2019-01-31 17:38 ` Waiman Long
2019-01-31 17:38 ` Waiman Long
2019-02-01 21:26 ` Alex Kogan
2019-02-01 21:26 ` Alex Kogan
2019-01-31 3:01 ` [PATCH 3/3] locking/qspinlock: Introduce starvation avoidance into CNA Alex Kogan
2019-01-31 3:01 ` Alex Kogan
2019-01-31 10:00 ` Peter Zijlstra [this message]
2019-01-31 10:00 ` Peter Zijlstra
2019-02-05 3:35 ` Alex Kogan
2019-02-05 3:35 ` Alex Kogan
2019-02-05 9:22 ` Peter Zijlstra
2019-02-05 9:22 ` Peter Zijlstra
2019-02-05 13:48 ` Waiman Long
2019-02-05 13:48 ` Waiman Long
2019-02-05 21:07 ` Alex Kogan
2019-02-05 21:07 ` Alex Kogan
2019-02-05 21:12 ` Waiman Long
2019-02-05 21:12 ` Waiman Long
2019-01-31 9:56 ` [PATCH 0/3] Add NUMA-awareness to qspinlock Peter Zijlstra
2019-01-31 9:56 ` Peter Zijlstra
2019-02-01 21:20 ` Alex Kogan
2019-02-01 21:20 ` Alex Kogan
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=20190131100009.GB31534@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alex.kogan@oracle.com \
--cc=arnd@arndb.de \
--cc=daniel.m.jordan@oracle.com \
--cc=dave.dice@oracle.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=rahul.x.yadav@oracle.com \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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