The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Austin Clements <amdragon+kernelbugzilla@mit.edu>,
	Ingo Molnar <mingo@elte.hu>, john stultz <johnstul@us.ibm.com>,
	Michael Kerrisk <mtk.manpages@googlemail.com>,
	Roland McGrath <roland@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] posix timers: use SIGQUEUE_CANCELLED when the timer is destroyed
Date: Sun, 18 May 2008 10:40:23 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805181038020.3020@woody.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0805181024050.3020@woody.linux-foundation.org>



On Sun, 18 May 2008, Linus Torvalds wrote:
> 
> So the rule is that if one bit of a word needs locking, then they *all* 
> do.

Side note: the alternative, of course, is to just use the atomic bit 
operations. They aren't generally much (if at all) faster than locking + 
doing the operation + unlocking, but they can avoid lock contention, so 
if you do a lot of bit ops that need no other locking than the setting and 
clearing (possibly with testing), then they are the right choice.

For signals, we obviously need other locking, so the atomic bit ops are a 
waste of time (doing *both* locking for other reasons *and* atomic bitops 
is obviously much slower than either).

		Linus

  reply	other threads:[~2008-05-18 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-17 15:14 [PATCH 3/3] posix timers: use SIGQUEUE_CANCELLED when the timer is destroyed Oleg Nesterov
2008-05-17 15:31 ` Oleg Nesterov
2008-05-17 17:11   ` Linus Torvalds
2008-05-18 17:15     ` Oleg Nesterov
2008-05-18 17:24       ` Linus Torvalds
2008-05-18 17:40         ` Linus Torvalds [this message]
2008-05-18 17:46         ` Oleg Nesterov
2008-05-21  2:27       ` Roland McGrath

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=alpine.LFD.1.10.0805181038020.3020@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=amdragon+kernelbugzilla@mit.edu \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mtk.manpages@googlemail.com \
    --cc=oleg@tv-sign.ru \
    --cc=roland@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox