All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Wang <wangyun@linux.vnet.ibm.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, dipankar@in.ibm.com
Subject: Re: [PATCH 0/7] rcu: optimize RCU trace on the huge platform
Date: Sat, 29 Sep 2012 10:32:31 +0800	[thread overview]
Message-ID: <50665DBF.6090106@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120928175301.GC2498@linux.vnet.ibm.com>

On 09/29/2012 01:53 AM, Paul E. McKenney wrote:
> On Thu, Sep 20, 2012 at 08:51:01AM +0800, Michael Wang wrote:
>> This patch set optimize the RCU trace to make it perform better on the
>> platform with thousands of cpus.
>>
>> The optimization including:
>> 	-- the cpu info will be separated by each flavor of rcu.
>> 	-- implement the 'cpu units sequence reading' to avoid losing data.
>>
>> Michael Wang (7):
>> 	[PATCH 1/7] rcu: create directory for each flavor of rcu
>> 	[PATCH 2/7] rcu: fundamental facility for 'cpu units sequence reading'
>> 	[PATCH 3/7] rcu: optimize the 'rcudata' for RCU trace
>> 	[PATCH 4/7] rcu: optimize the 'rcudata.csv' for RCU trace
>> 	[PATCH 5/7] rcu: optimize the 'rcu_pending' for RCU trace
>> 	[PATCH 6/7] rcu: replace the old interface with the new one
>> 	[PATCH 7/7] rcu: remove the interface "rcudata.csv"
>>
>> Signed-off-by: Michael Wang <wangyun@linux.vnet.ibm.com>
>> ---
>>  b/kernel/rcutree_trace.c |    8 +
>>  kernel/rcutree_trace.c   |  368 ++++++++++++++++++++---------------------------
>>  2 files changed, 170 insertions(+), 206 deletions(-)
> 
> Queued for 3.8, thank you Michael!

Thanks for your review.

Regards,
Michael Wang

> 
> 							Thanx, Paul
> 


      reply	other threads:[~2012-09-29  2:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1348102268-3544-1-git-send-email-wangyun@linux.vnet.ibm.com>
2012-09-28 17:53 ` [PATCH 0/7] rcu: optimize RCU trace on the huge platform Paul E. McKenney
2012-09-29  2:32   ` Michael Wang [this message]

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=50665DBF.6090106@linux.vnet.ibm.com \
    --to=wangyun@linux.vnet.ibm.com \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.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 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.