[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <491D6B4EAD0A714894D8AD22F4BDE0439F9ED2@SCYBEXDAG02.amd.com>
Date: Fri, 6 Apr 2012 17:47:28 +0000
From: "Chen, Dennis (SRDC SW)" <Dennis1.Chen@....com>
To: Clemens Ladisch <clemens@...isch.de>
CC: Ingo Molnar <mingo@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: semaphore and mutex in current Linux kernel (3.2.2)
On Fri, Apr 6, 2012 at 6:10 PM, Clemens Ladisch <clemens@...isch.de> wrote:
> Chen, Dennis (SRDC SW) wrote:
>> On Thu, Apr 5, 2012 at 10:15 PM, Clemens Ladisch <clemens@...isch.de> wrote:
>>
>> I guess this is related with RCU component, but I don't found the right place where the code
>> Located yet.
>
> "On the internet, nobody can hear you being subtle."
>
> If some other process wants to run on the same CPU, needs_resched() is set.
> (This might happen to make the cursor blink, for keyboard input, or when
> somebody starts a rogue process like ps.)
>
Hmm, I forget that in each timer interrupt, __rcu_pending() will be called, it will call
set_need_resched() to set the TIF_NEED_RESCHED in some condition...
The optimization of mutex work closely with rcu, so fantastic!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists