public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Christoph Hellwig <hch@ns.caldera.de>
Cc: Andrea Arcangeli <andrea@suse.de>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Paul McKenney <paul.mckenney@us.ibm.com>,
	mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New Read-Copy Update patch
Date: Tue, 5 Feb 2002 23:47:57 +0530	[thread overview]
Message-ID: <20020205234757.A427@in.ibm.com> (raw)
In-Reply-To: <20020205211826.B32506@in.ibm.com> <200202051654.g15GsWH01780@ns.caldera.de>
In-Reply-To: <200202051654.g15GsWH01780@ns.caldera.de>; from hch@ns.caldera.de on Tue, Feb 05, 2002 at 05:54:32PM +0100

On Tue, Feb 05, 2002 at 05:54:32PM +0100, Christoph Hellwig wrote:
> In article <20020205211826.B32506@in.ibm.com> you wrote:
> > 3. A per-cpu timer support ? - This will allow us to get rid of the krcud
> >    stuff and make RCU even simpler.
> 
> Something like http://people.redhat.com/mingo/scalable-timers-patches/smptimers-2.4.16-A0?

Almost. IIUC, there is still the possibility that a timer queued
in one CPU may get executed in another. While this by itself
doesn't cause a problem for this RCU implementation (we end up
checking some other CPU's queue), if one CPU is starved of timers,
it could be problematic.

Since we have many per-cpu data structures, it would be a useful thing
to have a per-cpu mechanism to manipulate these data structures
in a cache-sensitive way.

> 
> Ingo, Linus:  Any chance to see that in 2.5 soon?

IIRC, timerlist_lock used to show up in lockmetering in some workloads
we were using some time ago. It would be a good thing to get rid
of this global lock soon.

Thanks
Dipankar
-- 
Dipankar Sarma  <dipankar@in.ibm.com> http://lse.sourceforge.net
Linux Technology Center, IBM Software Lab, Bangalore, India.

  parent reply	other threads:[~2002-02-05 18:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 15:48 [PATCH] New Read-Copy Update patch Dipankar Sarma
2002-02-05 16:54 ` Christoph Hellwig
2002-02-05 16:57   ` Ingo Molnar
2002-02-05 18:41     ` Dipankar Sarma
2002-02-05 18:17   ` Dipankar Sarma [this message]
2002-02-05 17:13 ` Andrea Arcangeli
2002-02-05 18:34   ` Dipankar Sarma
2002-02-06  8:44     ` Daniel Phillips
2002-02-06  8:53       ` Dipankar Sarma
2002-02-06  8:58         ` Daniel Phillips
2002-02-06 10:47 ` [PATCH] New Read-Copy Update patch [fixed] Dipankar Sarma

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=20020205234757.A427@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=andrea@suse.de \
    --cc=hch@ns.caldera.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.mckenney@us.ibm.com \
    --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