From: John Levon <levon@movementarian.org>
To: Andrew Morton <akpm@osdl.org>
Cc: oprofile-list@lists.sourceforge.net,
linux-kernel@vger.kernel.org, jbarnes@sgi.com, anton@samba.org,
phil.el@wanadoo.fr
Subject: Re: [PATCH] improve OProfile on many-way systems
Date: Sun, 22 Aug 2004 00:22:06 +0100 [thread overview]
Message-ID: <20040821232206.GC20175@compsoc.man.ac.uk> (raw)
In-Reply-To: <20040821135833.6b1774a8.akpm@osdl.org>
On Sat, Aug 21, 2004 at 01:58:33PM -0700, Andrew Morton wrote:
> > Anton prompted me to get this patch merged. It changes the core buffer
> > sync algorithm of OProfile to avoid global locks wherever possible.
> > Anton tested an earlier version of this patch with some success. I've
> > lightly tested this applied against 2.6.8.1-mm3 on my two-way machine.
>
> OK. Oprofile isn't the most commonly tested part of the kernel. Given
> that you've "lightly tested" it,
I hammered the patch with earlier kernel versions for some time a while
ago. But that was on a 2-way, which hardly counts as proper testing.
> how do we know when it has had sufficient testing for its swim upstream?
I thought one of the points of the mm tree was to give things some
testing first.
> Does Philippe have some test suite, perhaps?
He doesn't have access to any SMP machines at all, last I heard.
regards
john
next prev parent reply other threads:[~2004-08-21 23:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 19:26 [PATCH] improve OProfile on many-way systems John Levon
2004-08-21 20:58 ` Andrew Morton
2004-08-21 22:06 ` Jesse Barnes
2004-08-21 23:14 ` John Levon
2004-08-22 4:34 ` Anton Blanchard
2004-08-24 0:07 ` John Levon
2004-08-21 23:22 ` John Levon [this message]
2004-08-21 23:36 ` Andrew Morton
2004-08-21 23:55 ` John Levon
2004-08-22 4:41 ` Andrew Morton
2004-08-22 22:42 ` John Levon
2004-08-22 3:50 ` Anton Blanchard
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=20040821232206.GC20175@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=jbarnes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=phil.el@wanadoo.fr \
/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