All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: andrea@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10pre10aa1 (first spin to the vm rewrite included)
Date: Tue, 18 Sep 2001 12:05:59 +0530	[thread overview]
Message-ID: <20010918120559.A32241@in.ibm.com> (raw)

In article <20010917180914.I713@athlon.random> andrea@suse.de wrote:
> Some of the the main features of 2.4.10pre10aa1 are:

> o	rcu core included (thought it will be rewritten, I agreed with
> 	Dipankar that the per-cpu scheduling sequence number seems
> 	the best approch, such number can serve also as a statistic
> 	to usespace infact, it is very similar to Rusty's patch but it
> 	doesn't add any branch to the schedule fast path, he's rewriting
> 	the patch at the moment and I'll include it in the next release)

Sorry, in the latest patch I folded the per-cpu context switch counter into 
per-cpu counters for other quiescent states - user mode code and idle loop
in order to save on an extra compare making a single counter :-)
So, it is not much of a user space statistics anymore.

I can put that counter back, but I think eventually it may anyway
make sense to start using per-cpu statistics counters. As a matter
of fact we are working on a framework to support these. If we do
use per-cpu statistics counters later, RCU can make use of the
per-cpu context switch statistics counter.

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

             reply	other threads:[~2001-09-18  6:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-18  6:35 Dipankar Sarma [this message]
     [not found] <20010917180914.I713@athlon.random>
2001-09-18 14:52 ` 2.4.10pre10aa1 (first spin to the vm rewrite included) Olaf Zaplinski
2001-09-18 15:30   ` Mads Martin Joergensen

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=20010918120559.A32241@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.