From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
wfg@mail.ustc.edu.cn, levon@movementarian.org
Subject: Re: [PATCH] Make RCU task_struct safe for oprofile
Date: Sun, 27 Nov 2005 13:28:14 +0100 [thread overview]
Message-ID: <20051127122814.GA22692@elte.hu> (raw)
In-Reply-To: <20051126210726.GA5277@us.ibm.com>
* Paul E. McKenney <paulmck@us.ibm.com> wrote:
> Hello!
>
> Applying RCU to the task structure broke oprofile, because
> free_task_notify() can now be called from softirq. This means that
> the task_mortuary lock must be acquired with irq disabled in order to
> avoid intermittent self-deadlock. Since irq is now disabled, the
> critical section within process_task_mortuary() has been restructured
> to be O(1) in order to maximize scalability and minimize realtime
> latency degradation.
>
> Kudos to Wu Fengguang for finding this problem!
thanks, i applied this to the -rt tree.
Ingo
prev parent reply other threads:[~2005-11-27 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-26 21:07 [PATCH] Make RCU task_struct safe for oprofile Paul E. McKenney
2005-11-27 12:28 ` Ingo Molnar [this message]
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=20051127122814.GA22692@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=wfg@mail.ustc.edu.cn \
/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