public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Dipankar Sarma <dipankar@in.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	Rusty Russell <rusty@rustcorp.com.au>,
	Paul McKenney <paul.mckenney@us.ibm.com>
Subject: Re: [PATCH] New Read-Copy Update patch
Date: Tue, 5 Feb 2002 18:13:54 +0100	[thread overview]
Message-ID: <20020205181354.M3135@athlon.random> (raw)
In-Reply-To: <20020205211826.B32506@in.ibm.com>
In-Reply-To: <20020205211826.B32506@in.ibm.com>

On Tue, Feb 05, 2002 at 09:18:26PM +0530, Dipankar Sarma wrote:
> Here is a "new" Read-Copy update patch that tries to address
> many of the concerns with the previous RCU patches. The
> details of RCU are documented as usual at
> http://lse.sourceforge.net/locking/rcupdate.html.
> 
> Main features of rcu-2.5.3.patch -
> 
> 1. Unlike my previous patch based on the old DYNIX/ptx algorithm
>    this does not have any code in arch-dependent directories. This
>    should make Andrea happy ;-)
> 2. No overhead in fastpath other than a per-cpu counter increment
>    during context switch.
> 3. RCU callbacks maintained in per-cpu lists, so global locking
>    needs to be used only once in every quiescent cycle, not
>    for queueing RCU callbacks.
> 4. No changes to scheduler code.
> 5. No RCU, no overhead other than the context switch counter increment.

I think you attached the wrong patch, the below one is based on the
kernel thread that we don't need with the scheduler counter.

BTW, I'd like to point out that the schedule counter is likely to be at
zero cacheline cost.

Andrea

  parent reply	other threads:[~2002-02-05 17:13 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
2002-02-05 17:13 ` Andrea Arcangeli [this message]
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=20020205181354.M3135@athlon.random \
    --to=andrea@suse.de \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --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