public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe W Damasio <felipewd@terra.com.br>
To: Felipe W Damasio <felipewd@terra.com.br>
Cc: rusty@rustcorp.com.au,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel/futex.c: Uneeded memory barrier
Date: Fri, 12 Sep 2003 15:33:04 -0300	[thread overview]
Message-ID: <3F621160.5020502@terra.com.br> (raw)
In-Reply-To: <3F620E61.4080604@terra.com.br>

[-- Attachment #1: Type: text/plain, Size: 509 bytes --]

	It is easier to review the patch if you can actually read the patch ;)

Felipe

Felipe W Damasio wrote:
>     Hi Rusty,
> 
>     Patch against 2.6-test5.
> 
>     Kills an unneeded set_current_state after schedule_timeout, since it 
> already guarantees that the task will be TASK_RUNNING.
> 
>     Also, when setting the state to TASK_RUNNING, isn't that memory 
> barrier unneeded? Patch removes this memory barrier too.
> 
>     If it looks good, please consider applying.
> 
>     Thanks.
> 
> Felipe
> 

[-- Attachment #2: futex-state.patch --]
[-- Type: text/plain, Size: 498 bytes --]

--- linux-2.6.0-test5/kernel/futex.c.orig	2003-09-12 15:14:42.000000000 -0300
+++ linux-2.6.0-test5/kernel/futex.c	2003-09-12 15:14:56.000000000 -0300
@@ -381,13 +381,12 @@
 		 * We were woken already.
 		 */
 		spin_unlock(&futex_lock);
-		set_current_state(TASK_RUNNING);
+		__set_current_state(TASK_RUNNING);
 		return 0;
 	}
 
 	spin_unlock(&futex_lock);
 	time = schedule_timeout(time);
-	set_current_state(TASK_RUNNING);
 
 	/*
 	 * NOTE: we don't remove ourselves from the waitqueue because

  reply	other threads:[~2003-09-12 18:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-12 18:20 [PATCH] kernel/futex.c: Uneeded memory barrier Felipe W Damasio
2003-09-12 18:33 ` Felipe W Damasio [this message]
2003-09-15  9:39   ` Rusty Russell
2003-09-16 12:05     ` Jamie Lokier
2003-09-13 19:02 ` Jamie Lokier
2003-09-15  1:36   ` Rusty Russell
2003-09-14 11:39 ` Rusty Russell
2003-09-14 14:08   ` Jamie Lokier
2003-09-15  3:41     ` Rusty Russell
2003-09-15  9:23       ` Russell King
2003-09-15 16:32         ` Rusty Russell

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=3F621160.5020502@terra.com.br \
    --to=felipewd@terra.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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