public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] introduce sig_needs_tasklist() helper
Date: Mon, 20 Feb 2006 18:13:02 -0800	[thread overview]
Message-ID: <20060221021302.GR1480@us.ibm.com> (raw)
In-Reply-To: <43F76374.EDA3ED9D@tv-sign.ru>

On Sat, Feb 18, 2006 at 09:12:04PM +0300, Oleg Nesterov wrote:
> In my opinion this patch cleanups the code. Please
> say 'nack' if you think differently.
> 
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
> 
> --- 2.6.16-rc3/kernel/signal.c~4_SNT	2006-02-18 23:26:51.000000000 +0300
> +++ 2.6.16-rc3/kernel/signal.c	2006-02-18 23:43:23.000000000 +0300
> @@ -147,6 +147,9 @@ static kmem_cache_t *sigqueue_cachep;
>  #define sig_kernel_stop(sig) \
>  		(((sig) < SIGRTMIN)  && T(sig, SIG_KERNEL_STOP_MASK))
>  
> +#define sig_needs_tasklist(sig) \
> +		(((sig) < SIGRTMIN)  && T(sig, SIG_KERNEL_STOP_MASK | M(SIGCONT)))
> +
>  #define sig_user_defined(t, signr) \
>  	(((t)->sighand->action[(signr)-1].sa.sa_handler != SIG_DFL) &&	\
>  	 ((t)->sighand->action[(signr)-1].sa.sa_handler != SIG_IGN))
> @@ -1202,7 +1205,7 @@ kill_proc_info(int sig, struct siginfo *
>  	struct task_struct *p;
>  
>  	rcu_read_lock();
> -	if (unlikely(sig_kernel_stop(sig) || sig == SIGCONT)) {
> +	if (unlikely(sig_needs_tasklist(sig))) {
>  		read_lock(&tasklist_lock);
>  		acquired_tasklist_lock = 1;
>  	}

Seems to me to be an improvement, but why not also encapsulate the
lock acquisition, something like:

	static inline int sig_tasklist_lock(int sig)
	{
		if (unlikely(sig_needs_tasklist(sig)) {
			read_lock(&tasklist_lock);
			return 1;
		}
		return 0;
	}

	static inline void sig_tasklist_unlock(int acquired_tasklist_lock)
	{
		if (acquired_tasklist_lock)
			read_unlock(&tasklist_lock);
	}

	...

	rcu_read_lock();
	acquired_tasklist_lock = sig_tasklist_lock(sig);

	...

	sig_tasklist_unlock(acquired_tasklist_lock);

Seem reasonable?

						Thanx, Paul

  reply	other threads:[~2006-02-21  2:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-18 18:12 [PATCH] introduce sig_needs_tasklist() helper Oleg Nesterov
2006-02-21  2:13 ` Paul E. McKenney [this message]
2006-02-21 18:25   ` Oleg Nesterov
2006-02-21 18:40     ` Paul E. McKenney

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=20060221021302.GR1480@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@tv-sign.ru \
    /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