From: Harvey Harrison <harvey.harrison@gmail.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org,
Matthew Wilcox <willy@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] semaphore: remove likely/unlikely annotations
Date: Thu, 28 Feb 2008 18:47:22 -0800 [thread overview]
Message-ID: <1204253242.20280.117.camel@brick> (raw)
In-Reply-To: <1204252679.20280.115.camel@brick>
Also some small codingstyle changes, empty line after declarations,
separate an if statement.
Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
---
I know it's a small thing, feel free to take it or not.
kernel/semaphore.c | 28 +++++++++++++++-------------
1 files changed, 15 insertions(+), 13 deletions(-)
diff --git a/kernel/semaphore.c b/kernel/semaphore.c
index 32934f2..f4aeeda 100644
--- a/kernel/semaphore.c
+++ b/kernel/semaphore.c
@@ -41,7 +41,7 @@ void down(struct semaphore *sem)
{
might_sleep();
spin_lock_irq(&sem->lock);
- if (unlikely(sem->count-- <= 0))
+ if (sem->count-- <= 0)
__down(sem);
spin_unlock_irq(&sem->lock);
}
@@ -50,9 +50,10 @@ EXPORT_SYMBOL(down);
int down_interruptible(struct semaphore *sem)
{
int result = 0;
+
might_sleep();
spin_lock_irq(&sem->lock);
- if (unlikely(sem->count-- <= 0))
+ if (sem->count-- <= 0)
result = __down_interruptible(sem);
spin_unlock_irq(&sem->lock);
return result;
@@ -62,9 +63,10 @@ EXPORT_SYMBOL(down_interruptible);
int down_killable(struct semaphore *sem)
{
int result = 0;
+
might_sleep();
spin_lock_irq(&sem->lock);
- if (unlikely(sem->count-- <= 0))
+ if (sem->count-- <= 0)
result = __down_killable(sem);
spin_unlock_irq(&sem->lock);
return result;
@@ -91,7 +93,7 @@ int down_trylock(struct semaphore *sem)
spin_lock_irqsave(&sem->lock, flags);
count = sem->count - 1;
- if (likely(count >= 0))
+ if (count >= 0)
sem->count = count;
spin_unlock_irqrestore(&sem->lock, flags);
return (count < 0);
@@ -103,7 +105,7 @@ void up(struct semaphore *sem)
unsigned long flags;
spin_lock_irqsave(&sem->lock, flags);
- if (likely(sem->count >= 0))
+ if (sem->count >= 0)
sem->count++;
else
__up(sem);
@@ -128,8 +130,9 @@ struct semaphore_waiter {
*/
static void noinline __sched __up_down_common(struct semaphore *sem)
{
- struct semaphore_waiter *waiter = list_first_entry(&sem->wait_list,
- struct semaphore_waiter, list);
+ struct semaphore_waiter *waiter;
+
+ waiter = list_first_entry(&sem->wait_list, struct semaphore_waiter, list);
list_del(&waiter->list);
waiter->up = 1;
wake_up_process(waiter->task);
@@ -150,10 +153,9 @@ static inline int __sched __down_common(struct semaphore *sem, long state)
waiter.up = 0;
for (;;) {
- if (unlikely((state == TASK_INTERRUPTIBLE &&
- signal_pending(task)) ||
- (state == TASK_KILLABLE &&
- fatal_signal_pending(task))))
+ if (state == TASK_INTERRUPTIBLE && signal_pending(task))
+ goto interrupted;
+ if (state == TASK_KILLABLE && fatal_signal_pending(task))
goto interrupted;
__set_task_state(task, state);
spin_unlock_irq(&sem->lock);
@@ -175,7 +177,7 @@ static inline int __sched __down_common(struct semaphore *sem, long state)
* but it doesn't hurt, that's not a commonly exercised path and
* it's not a performance path either.
*/
- if (unlikely((++sem->count >= 0) && !list_empty(&sem->wait_list)))
+ if (++sem->count >= 0 && !list_empty(&sem->wait_list))
__up_down_common(sem);
return result;
}
@@ -197,7 +199,7 @@ static int noinline __sched __down_killable(struct semaphore *sem)
static void noinline __sched __up(struct semaphore *sem)
{
- if (unlikely(list_empty(&sem->wait_list)))
+ if (list_empty(&sem->wait_list))
sem->count++;
else
__up_down_common(sem);
--
1.5.4.3.342.g99e8
next prev parent reply other threads:[~2008-02-29 2:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 0:36 [PATCHES] semaphore rewrite Matthew Wilcox
2008-02-28 6:33 ` [PATCH 01/12] Fix quota.h includes Matthew Wilcox
2008-02-28 6:33 ` [PATCH 02/12] Add semaphore.h to kernel_lock.c Matthew Wilcox
2008-02-28 6:33 ` [PATCH 03/12] arch: Remove unnecessary inclusions of asm/semaphore.h Matthew Wilcox
2008-02-28 6:33 ` [PATCH 04/12] net: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 05/12] drivers: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 06/12] fs: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 07/12] include: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 08/12] kernel: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 09/12] lib: " Matthew Wilcox
2008-02-28 6:33 ` [PATCH 10/12] security: " Matthew Wilcox
2008-02-28 6:34 ` [PATCH 11/12] Generic semaphore implementation Matthew Wilcox
2008-02-28 6:34 ` [PATCH 12/12] Convert asm/semaphore.h users to linux/semaphore.h Matthew Wilcox
2008-02-28 7:18 ` [PATCH 11/12] Generic semaphore implementation Ingo Molnar
2008-02-29 0:39 ` Matthew Wilcox
2008-02-29 0:50 ` Harvey Harrison
2008-02-29 1:43 ` Andrew Morton
2008-02-29 5:30 ` Matthew Wilcox
2008-02-29 17:42 ` Haavard Skinnemoen
2008-02-29 19:21 ` Ingo Molnar
2008-02-29 2:00 ` Stephen Rothwell
2008-02-29 2:10 ` Andrew Morton
2008-02-29 5:32 ` Matthew Wilcox
2008-02-29 6:43 ` Stephen Rothwell
2008-02-29 16:14 ` Linus Torvalds
2008-02-29 1:57 ` Andrew Morton
2008-02-29 5:43 ` Matthew Wilcox
2008-02-29 2:37 ` Harvey Harrison
2008-02-29 2:47 ` Harvey Harrison [this message]
2008-03-03 14:54 ` Matthew Wilcox
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=1204253242.20280.117.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=willy@linux.intel.com \
/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