public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@engr.sgi.com>
To: paulmck@us.ibm.com
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	hawkes@sgi.com, linux-kernel@vger.kernel.org, wli@holomorphy.com,
	manfred@dbl.q-ag.de
Subject: Re: kernbench on 512p
Date: Fri, 20 Aug 2004 13:24:32 -0400	[thread overview]
Message-ID: <200408201324.32464.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <20040820155717.GF1243@us.ibm.com>

On Friday, August 20, 2004 11:57 am, Paul E. McKenney wrote:
> If I am not too confused, you need #4 and #5 out of Manfred's set of
> five RCU_HUGE patchset.  They are at:
>
> 	http://marc.theaimsgroup.com/?l=linux-kernel&m=108546358123902&w=2
> 	http://marc.theaimsgroup.com/?l=linux-kernel&m=108546384711797&w=2
>
> A little work will be required to get them to apply.  For example, in
> the first patch, instead of:
>
> 	spin_lock(&rcu_state.mutex);
>
> one would say:
>
> 	spin_lock(&rsp->lock);
>
> due to the addition of the _bh() primitives.  The "rcu_ctrlblk."
> and "rcu_state." have been replaced by pointers in order to handle
> multiple different types of grace periods:
>
> o	Traditional grace periods based on context switch, executing
> 	in user mode, or running the idle loop.
>
> o	New-age low-latency grace periods based on running with
> 	interrupts enabled.

Looks like a bit more context has changed.  Manfred, care to respin against 
-mm3 so I can test?

Thanks,
Jesse

  reply	other threads:[~2004-08-20 17:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-19 16:16 kernbench on 512p Jesse Barnes
2004-08-19 16:22 ` William Lee Irwin III
2004-08-19 16:29 ` David Mosberger
2004-08-19 16:37   ` Jesse Barnes
2004-08-19 16:40     ` David Mosberger
2004-08-19 17:55       ` Alan Cox
2004-08-20  7:53         ` David Mosberger
2004-08-19 18:25     ` Martin J. Bligh
2004-08-19 18:42       ` Jesse Barnes
2004-08-19 21:11       ` Jesse Barnes
2004-08-19 21:24         ` Jesse Barnes
2004-08-19 21:56           ` Martin J. Bligh
2004-08-20 19:36             ` Maneesh Soni
2004-08-19 23:38           ` Paul E. McKenney
2004-08-20  0:16             ` Jesse Barnes
2004-08-20 15:57               ` Paul E. McKenney
2004-08-20 17:24                 ` Jesse Barnes [this message]
2004-08-20 19:22                   ` Manfred Spraul
2004-08-20 20:19                   ` Manfred Spraul
2004-08-23 21:23                     ` Jesse Barnes
2004-08-23 23:13                       ` Jesse Barnes
2004-09-10 19:01                     ` Greg Edwards
2004-09-13 18:21                       ` Manfred Spraul
2004-09-14 17:52                         ` Greg Edwards
2004-09-14 18:16                           ` Manfred Spraul
2004-09-14 18:43                             ` Greg Edwards
2004-09-14 19:16                               ` Manfred Spraul
2004-08-19 21:50         ` Ray Bryant
2004-08-19 22:00           ` Jesse Barnes
2004-08-19 23:03 ` William Lee Irwin III
2004-08-20 17:35   ` William Lee Irwin III
2004-08-20  0:56 ` remove dentry_open::file_ra_init_state() duplicated memset was " Marcelo Tosatti
2004-08-20  6:21   ` Andrew Morton
2004-08-20  7:28     ` Marcelo Tosatti
2004-08-20  8:34       ` Andrew Morton

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=200408201324.32464.jbarnes@engr.sgi.com \
    --to=jbarnes@engr.sgi.com \
    --cc=hawkes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@dbl.q-ag.de \
    --cc=mbligh@aracnet.com \
    --cc=paulmck@us.ibm.com \
    --cc=wli@holomorphy.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