public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux-foundation.org>
To: Bruno Santos <bsantos@av.it.pt>
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: semaphore: lockless fastpath using atomic_{inc,dec}_return
Date: Wed, 09 Jul 2008 09:24:42 -0500	[thread overview]
Message-ID: <4874CA2A.3050600@linux-foundation.org> (raw)
In-Reply-To: <20080709071635.5c5ecc0f@infradead.org>

And is this safe? It seems that we can always be rescheduled after the atomic operation and
interrupts can occur too. You need to tell us why this is safe in all cases.


  reply	other threads:[~2008-07-09 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-09 13:13 semaphore: lockless fastpath using atomic_{inc,dec}_return Bruno Santos
2008-07-09 14:16 ` Arjan van de Ven
2008-07-09 14:24   ` Christoph Lameter [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-07-09 15:39 Bruno Santos
2008-07-09 15:50 ` Arjan van de Ven
2008-07-09 16:56   ` Bruno Santos
2008-07-09 19:27     ` Bruno Santos
2008-07-09 20:05     ` Arjan van de Ven

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=4874CA2A.3050600@linux-foundation.org \
    --to=cl@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=bsantos@av.it.pt \
    --cc=linux-kernel@vger.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