All of lore.kernel.org
 help / color / mirror / Atom feed
From: Waiman Long <waiman.long@hpe.com>
To: Waiman Long <Waiman.Long@hpe.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>, Oleg Nesterov <oleg@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>, Stas Sergeev <stsp@list.ru>,
	<linux-kernel@vger.kernel.org>,
	Scott J Norton <scott.norton@hpe.com>,
	Douglas Hatch <doug.hatch@hpe.com>
Subject: Re: [PATCH v3] signals: Avoid unnecessary taking of sighand->siglock
Date: Tue, 18 Oct 2016 12:12:40 -0400	[thread overview]
Message-ID: <580649F8.2080809@hpe.com> (raw)
In-Reply-To: <1474979209-11867-1-git-send-email-Waiman.Long@hpe.com>

On 09/27/2016 08:26 AM, Waiman Long wrote:
> When running certain database workload on a high-end system with many
> CPUs, it was found that spinlock contention in the sigprocmask syscalls
> became a significant portion of the overall CPU cycles as shown below.
>
>    9.30%  9.30%  905387  dataserver  /proc/kcore 0x7fff8163f4d2
>    [k] _raw_spin_lock_irq
>              |
>              ---_raw_spin_lock_irq
>                 |
>                 |--99.34%-- __set_current_blocked
>                 |          sigprocmask
>                 |          sys_rt_sigprocmask
>                 |          system_call_fastpath
>                 |          |
>                 |          |--50.63%-- __swapcontext
>                 |          |          |
>                 |          |          |--99.91%-- upsleepgeneric
>                 |          |
>                 |          |--49.36%-- __setcontext
>                 |          |          ktskRun
>
> Looking further into the swapcontext function in glibc, it was found
> that the function always call sigprocmask() without checking if there
> are changes in the signal mask.
>
> A check was added to the __set_current_blocked() function to avoid
> taking the sighand->siglock spinlock if there is no change in the
> signal mask. This will prevent unneeded spinlock contention when many
> threads are trying to call sigprocmask().
>
> With this patch applied, the spinlock contention in sigprocmask() was
> gone.
>
> Signed-off-by: Waiman Long<Waiman.Long@hpe.com>
> ---
>   v2->v3:
>     - Add a sigequalsets() helper in signal.h and use it for comparison.
>
>   v1->v2:
>     - Fix compiler warning in mips.
>
>   include/linux/signal.h |   17 +++++++++++++++++
>   kernel/signal.c        |    7 +++++++
>   2 files changed, 24 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/signal.h b/include/linux/signal.h
> index b63f63e..5308304 100644
> --- a/include/linux/signal.h
> +++ b/include/linux/signal.h
> @@ -97,6 +97,23 @@ static inline int sigisemptyset(sigset_t *set)
>   	}
>   }
>
> +static inline int sigequalsets(const sigset_t *set1, const sigset_t *set2)
> +{
> +	switch (_NSIG_WORDS) {
> +	case 4:
> +		return	(set1->sig[3] == set2->sig[3])&&
> +			(set1->sig[2] == set2->sig[2])&&
> +			(set1->sig[1] == set2->sig[1])&&
> +			(set1->sig[0] == set2->sig[0]);
> +	case 2:
> +		return	(set1->sig[1] == set2->sig[1])&&
> +			(set1->sig[0] == set2->sig[0]);
> +	case 1:
> +		return	set1->sig[0] == set2->sig[0];
> +	}
> +	return 0;
> +}
> +
>   #define sigmask(sig)	(1UL<<  ((sig) - 1))
>
>   #ifndef __HAVE_ARCH_SIG_SETOPS
> diff --git a/kernel/signal.c b/kernel/signal.c
> index af21afc..04e8f50 100644
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2485,6 +2485,13 @@ void __set_current_blocked(const sigset_t *newset)
>   {
>   	struct task_struct *tsk = current;
>
> +	/*
> +	 * In case the signal mask hasn't changed, there is nothing we need
> +	 * to do. The current->blocked shouldn't be modified by other task.
> +	 */
> +	if (sigequalsets(&tsk->blocked, newset))
> +		return;
> +
>   	spin_lock_irq(&tsk->sighand->siglock);
>   	__set_task_blocked(tsk, newset);
>   	spin_unlock_irq(&tsk->sighand->siglock);

This is a pretty simple patch. Is that a chance that it can be pulled 
into 4.10?

Cheers,
Longman

      parent reply	other threads:[~2016-10-18 16:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 12:26 [PATCH v3] signals: Avoid unnecessary taking of sighand->siglock Waiman Long
2016-09-27 16:17 ` Oleg Nesterov
2016-09-27 18:21   ` Waiman Long
2016-10-18 16:12 ` 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=580649F8.2080809@hpe.com \
    --to=waiman.long@hpe.com \
    --cc=akpm@linux-foundation.org \
    --cc=doug.hatch@hpe.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=scott.norton@hpe.com \
    --cc=stsp@list.ru \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.