From: Waiman Long <longman@redhat.com>
To: Alex Kogan <alex.kogan@oracle.com>,
linux@armlinux.org.uk, peterz@infradead.org, mingo@redhat.com,
will.deacon@arm.com, arnd@arndb.de, linux-arch@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, tglx@linutronix.de, bp@alien8.de,
hpa@zytor.com, x86@kernel.org, guohanjun@huawei.com,
jglauber@marvell.com
Cc: steven.sistare@oracle.com, daniel.m.jordan@oracle.com,
dave.dice@oracle.com, rahul.x.yadav@oracle.com
Subject: Re: [PATCH v7 4/5] locking/qspinlock: Introduce starvation avoidance into CNA
Date: Fri, 6 Dec 2019 13:09:40 -0500 [thread overview]
Message-ID: <3d06a43e-0cf7-dc47-a2c7-7a9145a29ad5@redhat.com> (raw)
In-Reply-To: <20191125210709.10293-5-alex.kogan@oracle.com>
On 11/25/19 4:07 PM, Alex Kogan wrote:
> Keep track of the number of intra-node lock handoffs, and force
> inter-node handoff once this number reaches a preset threshold.
> The default value for the threshold can be overridden with
> the new kernel boot command-line option "numa_spinlock_threshold".
>
> Signed-off-by: Alex Kogan <alex.kogan@oracle.com>
> Reviewed-by: Steve Sistare <steven.sistare@oracle.com>
> ---
> .../admin-guide/kernel-parameters.txt | 8 ++++++
> arch/x86/kernel/alternative.c | 27 +++++++++++++++++++
> kernel/locking/qspinlock.c | 3 +++
> kernel/locking/qspinlock_cna.h | 27 ++++++++++++++++---
> 4 files changed, 62 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 904cb32f592d..887fbfce701d 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -3185,6 +3185,14 @@
> Not specifying this option is equivalent to
> numa_spinlock=auto.
>
> + numa_spinlock_threshold= [NUMA, PV_OPS]
> + Set the threshold for the number of intra-node
> + lock hand-offs before the NUMA-aware spinlock
> + is forced to be passed to a thread on another NUMA node.
> + Valid values are in the [0..31] range. Smaller values
> + result in a more fair, but less performant spinlock, and
> + vice versa. The default value is 16.
> +
> cpu0_hotplug [X86] Turn on CPU0 hotplug feature when
> CONFIG_BOOTPARAM_HOTPLUG_CPU0 is off.
> Some features depend on CPU0. Known dependencies are:
> diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
> index 6a4ccbf4e09c..28552e0491b5 100644
> --- a/arch/x86/kernel/alternative.c
> +++ b/arch/x86/kernel/alternative.c
> @@ -723,6 +723,33 @@ static int __init numa_spinlock_setup(char *str)
>
> __setup("numa_spinlock=", numa_spinlock_setup);
>
> +/*
> + * Controls the threshold for the number of intra-node lock hand-offs before
> + * the NUMA-aware variant of spinlock is forced to be passed to a thread on
> + * another NUMA node. By default, the chosen value provides reasonable
> + * long-term fairness without sacrificing performance compared to a lock
> + * that does not have any fairness guarantees.
> + */
> +int intra_node_handoff_threshold = 1 << 16;
^
__ro_after_init
> +
> +static int __init numa_spinlock_threshold_setup(char *str)
> +{
> + int new_threshold_param;
> +
> + if (get_option(&str, &new_threshold_param)) {
> + /* valid value is between 0 and 31 */
> + if (new_threshold_param < 0 || new_threshold_param > 31)
> + return 0;
> +
> + intra_node_handoff_threshold = 1 << new_threshold_param;
> + return 1;
> + }
> +
> + return 0;
> +}
> +
> +__setup("numa_spinlock_threshold=", numa_spinlock_threshold_setup);
> +
> #endif
>
Against, this should be in qspinlock_can.h not in alternative.c.
Cheers,
Longman
next prev parent reply other threads:[~2019-12-06 18:09 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 21:07 [PATCH v7 0/5] Add NUMA-awareness to qspinlock Alex Kogan
2019-11-25 21:07 ` Alex Kogan
2019-11-25 21:07 ` [PATCH v7 1/5] locking/qspinlock: Rename mcs lock/unlock macros and make them more generic Alex Kogan
2019-11-25 21:07 ` Alex Kogan
2020-01-22 9:15 ` Peter Zijlstra
2020-01-22 9:15 ` Peter Zijlstra
[not found] ` <C608A39E-CAFC-4C79-9EB6-3DFD9621E3F6@oracle.com>
2020-01-25 11:23 ` Peter Zijlstra
2020-01-25 11:23 ` Peter Zijlstra
2019-11-25 21:07 ` [PATCH v7 2/5] locking/qspinlock: Refactor the qspinlock slow path Alex Kogan
2019-11-25 21:07 ` Alex Kogan
2019-11-25 21:07 ` [PATCH v7 3/5] locking/qspinlock: Introduce CNA into the slow path of qspinlock Alex Kogan
2019-11-25 21:07 ` Alex Kogan
2019-12-06 17:21 ` Waiman Long
2019-12-06 17:21 ` Waiman Long
2019-12-06 19:50 ` Alex Kogan
2019-12-06 19:50 ` Alex Kogan
2020-01-21 20:29 ` Peter Zijlstra
2020-01-21 20:29 ` Peter Zijlstra
2020-01-22 8:58 ` Will Deacon
2020-01-22 9:22 ` Peter Zijlstra
2020-01-22 9:22 ` Peter Zijlstra
2020-01-22 9:51 ` Peter Zijlstra
2020-01-22 9:51 ` Peter Zijlstra
2020-01-22 17:04 ` Peter Zijlstra
2020-01-22 17:04 ` Peter Zijlstra
2020-01-23 9:00 ` Peter Zijlstra
2020-01-23 9:00 ` Peter Zijlstra
2020-01-30 22:01 ` Alex Kogan
2020-01-31 13:35 ` Peter Zijlstra
2020-01-31 13:35 ` Peter Zijlstra
2020-01-31 18:33 ` Alex Kogan
2020-01-31 18:33 ` Alex Kogan
2019-11-25 21:07 ` [PATCH v7 4/5] locking/qspinlock: Introduce starvation avoidance into CNA Alex Kogan
2019-11-25 21:07 ` Alex Kogan
2019-12-06 18:09 ` Waiman Long [this message]
2019-12-06 18:09 ` Waiman Long
2019-11-25 21:07 ` [PATCH v7 5/5] locking/qspinlock: Introduce the shuffle reduction optimization " Alex Kogan
2019-11-25 21:07 ` Alex Kogan
2019-12-06 22:00 ` Waiman Long
2019-12-06 22:00 ` Waiman Long
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=3d06a43e-0cf7-dc47-a2c7-7a9145a29ad5@redhat.com \
--to=longman@redhat.com \
--cc=alex.kogan@oracle.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=daniel.m.jordan@oracle.com \
--cc=dave.dice@oracle.com \
--cc=guohanjun@huawei.com \
--cc=hpa@zytor.com \
--cc=jglauber@marvell.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=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rahul.x.yadav@oracle.com \
--cc=steven.sistare@oracle.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
--cc=x86@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).