public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Paul E. McKenney" <paulmck@us.ibm.com>,
	linux-kernel@vger.kernel.org, tytso@us.ibm.com,
	sripathi@in.ibm.com, dipankar@in.ibm.com, oleg@tv-sign.ru
Subject: Re: [RFC,PATCH] RCUify single-thread case of clock_gettime()
Date: Mon, 31 Oct 2005 22:50:44 +0100	[thread overview]
Message-ID: <20051031215044.GA20926@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.61.0510312004460.10705@goblin.wat.veritas.com>


* Hugh Dickins <hugh@veritas.com> wrote:

> On Mon, 31 Oct 2005, Ingo Molnar wrote:
> > * Hugh Dickins <hugh@veritas.com> wrote:
> > > 
> > > Not my area at all, but this looks really dodgy to me, Paul:
> > > could you explain it further?
> > 
> > the patch below (included in the -rt tree) is the prerequisite. That's 
> > what Paul's "requires RCU on task_struct" comment refers to.
> 
> Thanks, Ingo: Sorry, Paul: I missed that it was an -rt patch: Ignore 
> me.

btw., since the RCU-task-struct thing is beneficial to upstream SMP 
kernels (even without any preempt option enabled), it should be 
considered for upstream too. The tasklist_lock is one of our last 
remaining monolithic and globally-bouncing locks. The patch i attached 
to the previous mail is against the upstream kernel and implements the 
RCU-task-struct logic, without any PREEMPT_RT dependency. (the -rt tree 
is a collection of various preemption related patches, not just 
PREEMPT_RT)

	Ingo

  reply	other threads:[~2005-10-31 21:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 17:44 [RFC,PATCH] RCUify single-thread case of clock_gettime() Paul E. McKenney
2005-10-31 18:08 ` Hugh Dickins
2005-10-31 19:54   ` Ingo Molnar
2005-10-31 20:07     ` Hugh Dickins
2005-10-31 21:50       ` Ingo Molnar [this message]
2005-10-31 19:37 ` Joe Seigh
2005-10-31 21:44 ` Ingo Molnar

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=20051031215044.GA20926@elte.hu \
    --to=mingo@elte.hu \
    --cc=dipankar@in.ibm.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    --cc=paulmck@us.ibm.com \
    --cc=sripathi@in.ibm.com \
    --cc=tytso@us.ibm.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