From: Randy Dunlap <rdunlap@infradead.org>
To: Alex Kogan <alex.kogan@oracle.com>,
linux@armlinux.org.uk, peterz@infradead.org, 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, 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
Subject: Re: [PATCH v11 4/5] locking/qspinlock: Introduce starvation avoidance into CNA
Date: Tue, 15 Sep 2020 12:24:26 -0700 [thread overview]
Message-ID: <8019917d-5e8e-e03d-583c-6809dee7a5c2@infradead.org> (raw)
In-Reply-To: <20200915180535.2975060-5-alex.kogan@oracle.com>
Hi,
Entries in the kernel-parameters.txt file should be kept in alphabetical order
mostly (there are a few exceptions where related options are kept together).
On 9/15/20 11:05 AM, Alex Kogan wrote:
> Keep track of the time the thread at the head of the secondary queue
> has been waiting, and force inter-node handoff once this time passes
> a preset threshold. The default value for the threshold (10ms) can be
> overridden with the new kernel boot command-line option
> "numa_spinlock_threshold". The ms value is translated internally to the
> nearest rounded-up jiffies.
>
> Signed-off-by: Alex Kogan <alex.kogan@oracle.com>
> Reviewed-by: Steve Sistare <steven.sistare@oracle.com>
> Reviewed-by: Waiman Long <longman@redhat.com>
> ---
> .../admin-guide/kernel-parameters.txt | 9 ++
> kernel/locking/qspinlock_cna.h | 95 ++++++++++++++++---
> 2 files changed, 92 insertions(+), 12 deletions(-)
>
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 51ce050f8701..73ab23a47b97 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -3363,6 +3363,15 @@
> Not specifying this option is equivalent to
> numa_spinlock=auto.
>
> + numa_spinlock_threshold= [NUMA, PV_OPS]
> + Set the time threshold in milliseconds 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 [1..100] range. Smaller values result
> + in a more fair, but less performant spinlock,
> + and vice versa. The default value is 10.
> +
> cpu0_hotplug [X86] Turn on CPU0 hotplug feature when
> CONFIG_BOOTPARAM_HOTPLUG_CPU0 is off.
> Some features depend on CPU0. Known dependencies are:
This new entry and numa_spinlock from patch 3/5 should go between these other 2 NUMA entries:
numa_balancing= [KNL,X86] Enable or disable automatic NUMA balancing.
Allowed values are enable and disable
numa_zonelist_order= [KNL, BOOT] Select zonelist order for NUMA.
'node', 'default' can be specified
This can be set from sysctl after boot.
See Documentation/admin-guide/sysctl/vm.rst for details.
Oooh, that cpu0_hotplug entry is way out of place. I'll send a patch for that.
thanks.
--
~Randy
next prev parent reply other threads:[~2020-09-15 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 18:05 [PATCH v11 0/5] Add NUMA-awareness to qspinlock Alex Kogan
2020-09-15 18:05 ` [PATCH v11 1/5] locking/qspinlock: Rename mcs lock/unlock macros and make them more generic Alex Kogan
2020-09-15 18:05 ` [PATCH v11 2/5] locking/qspinlock: Refactor the qspinlock slow path Alex Kogan
2020-09-15 18:05 ` [PATCH v11 3/5] locking/qspinlock: Introduce CNA into the slow path of qspinlock Alex Kogan
2020-09-16 2:40 ` Waiman Long
2020-09-15 18:05 ` [PATCH v11 4/5] locking/qspinlock: Introduce starvation avoidance into CNA Alex Kogan
2020-09-15 19:24 ` Randy Dunlap [this message]
2020-09-15 19:57 ` Alex Kogan
2020-09-16 3:13 ` Waiman Long
2020-09-15 18:05 ` [PATCH v11 5/5] locking/qspinlock: Avoid moving certain threads between waiting queues in CNA 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=8019917d-5e8e-e03d-583c-6809dee7a5c2@infradead.org \
--to=rdunlap@infradead.org \
--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=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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