All of lore.kernel.org
 help / color / mirror / Atom feed
From: npiggin@nick.local0.net
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [patch 2/5] tasklet: use lock bitops for tasklet lock
Date: Wed, 24 Oct 2007 18:13:07 +1000	[thread overview]
Message-ID: <20071024081405.202232000@nick.local0.net> (raw)
In-Reply-To: 20071024081305.906617000@nick.local0.net

[-- Attachment #1: tasklet_lock-use-lock-bitops.patch --]
[-- Type: text/plain, Size: 845 bytes --]

Signed-off-by: Nick Piggin <npiggin@suse.de>

---
 include/linux/interrupt.h |    5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

Index: linux-2.6/include/linux/interrupt.h
===================================================================
--- linux-2.6.orig/include/linux/interrupt.h
+++ linux-2.6/include/linux/interrupt.h
@@ -321,13 +321,12 @@ enum
 #ifdef CONFIG_SMP
 static inline int tasklet_trylock(struct tasklet_struct *t)
 {
-	return !test_and_set_bit(TASKLET_STATE_RUN, &(t)->state);
+	return !test_and_set_bit_lock(TASKLET_STATE_RUN, &(t)->state);
 }
 
 static inline void tasklet_unlock(struct tasklet_struct *t)
 {
-	smp_mb__before_clear_bit(); 
-	clear_bit(TASKLET_STATE_RUN, &(t)->state);
+	clear_bit_unlock(TASKLET_STATE_RUN, &(t)->state);
 }
 
 static inline void tasklet_unlock_wait(struct tasklet_struct *t)

-- 


  parent reply	other threads:[~2007-10-24  9:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24  8:13 [patch 0/5] lock bitops patches npiggin
2007-10-24  8:13 ` [patch 1/5] wait: use lock bitops for __wait_on_bit_lock npiggin
2007-10-25  1:14   ` Andrew Morton
2007-10-25  2:17     ` Nick Piggin
2007-10-11 20:56       ` Pavel Machek
2007-10-24  8:13 ` npiggin [this message]
2007-10-24  8:13 ` [patch 3/5] mm: rename page lock npiggin
2007-10-24  8:13 ` [patch 4/5] mm: use lock bitops for " npiggin
2007-10-24  8:13 ` [patch 5/5] fs: use lock bitops for the buffer lock npiggin

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=20071024081405.202232000@nick.local0.net \
    --to=npiggin@nick.local0.net \
    --cc=akpm@linux-foundation.org \
    --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 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.