All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: "Chen, Tim C" <tim.c.chen@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, "Siddha,
	Suresh B" <suresh.b.siddha@intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Daniel Walker <dwalker@mvista.com>
Subject: Re: [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch
Date: Wed, 3 Jan 2007 17:27:09 -0800	[thread overview]
Message-ID: <20070104012709.GC31943@gnuppy.monkey.org> (raw)
In-Reply-To: <9D2C22909C6E774EBFB8B5583AE5291C01A4FBE5@fmsmsx414.amr.corp.intel.com>

On Wed, Jan 03, 2007 at 05:11:04PM -0800, Chen, Tim C wrote:
> Bill Huey (hui) wrote:
> > 
> > Thanks, the numbers look a bit weird in that the first column should
> > have a bigger number of events than that second column since it is a
> > special case subset. Looking at the lock_stat_note() code should show
> > that to be the case. Did you make a change to the output ?
> 
> No, I did not change the output.  I did reset to the contention content
> 
> by doing echo "0" > /proc/lock_stat/contention.
> 
> I noticed that the first column get reset but not the second column. So
> the reset code probably need to be checked.

This should have the fix. 

	http://mmlinux.sf.net/public/patch-2.6.20-rc2-rt2.3.lock_stat.patch

If you can rerun it and post the results, it'll hopefully show the behavior 
of that lock acquisition better.

Thanks

bill


  reply	other threads:[~2007-01-04  1:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-27  0:51 2.6.19-rt14 slowdown compared to 2.6.19 Chen, Tim C
2006-12-29 23:26 ` [PATCH] lock stat for -rt 2.6.20-rc2-rt2 [was Re: 2.6.19-rt14 slowdown compared to 2.6.19] Bill Huey
2006-12-30 11:19   ` Ingo Molnar
2006-12-30 14:56     ` Daniel Walker
2006-12-30 19:32       ` Bill Huey
2007-01-03  7:41     ` [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch Bill Huey
2007-01-03 23:59       ` Chen, Tim C
2007-01-04  0:12         ` Bill Huey
2007-01-04  0:25           ` Chen, Tim C
2007-01-04  0:29             ` Bill Huey
2007-01-04  0:46               ` Chen, Tim C
2007-01-04  1:00                 ` Bill Huey
2007-01-04  1:07                   ` Bill Huey
2007-01-04  1:11                   ` Chen, Tim C
2007-01-04  1:27                     ` Bill Huey [this message]
2007-01-04  2:14                       ` Chen, Tim C
2007-01-04  8:12                         ` Bill Huey
2007-01-04  4:46       ` Ingo Molnar
2007-01-24 23:06         ` Bill Huey
2007-01-25  8:39           ` Ingo Molnar
2007-01-24 11:31       ` Ingo Molnar
2007-01-24 22:52         ` Bill Huey
2007-01-02 22:51   ` [PATCH] lock stat for -rt 2.6.20-rc2-rt2 [was Re: 2.6.19-rt14 slowdown compared to 2.6.19] Chen, Tim C
2007-01-02 23:12     ` Bill Huey
2007-01-02 23:47       ` Bill Huey

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=20070104012709.GC31943@gnuppy.monkey.org \
    --to=billh@gnuppy.monkey.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=tim.c.chen@intel.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.