From: Jesse Barnes <jbarnes@sgi.com>
To: Andrew Morton <akpm@osdl.org>
Cc: John Levon <levon@movementarian.org>,
oprofile-list@lists.sourceforge.net,
linux-kernel@vger.kernel.org, anton@samba.org,
phil.el@wanadoo.fr
Subject: Re: [PATCH] improve OProfile on many-way systems
Date: Sat, 21 Aug 2004 18:06:31 -0400 [thread overview]
Message-ID: <200408211806.32566.jbarnes@sgi.com> (raw)
In-Reply-To: <20040821135833.6b1774a8.akpm@osdl.org>
On Saturday, August 21, 2004 4:58 pm, Andrew Morton wrote:
> John Levon <levon@movementarian.org> 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, how do we know when it has had sufficient
> testing for its swim upstream?
I'll give it a go on Monday, when I have some more time reserved on the 512p
system. Last time I tried enabling oprofile, the system wouldn't boot or at
least got so slow that I didn't want to wait for it (i.e. init started, but
the system pretty much hung part way through the init scripts).
If it boots, I'll try collecting some info. John, will the oprofile tools in
RHEL3 work with 2.6.8.1-mm3 + these patches?
Thanks,
Jesse
next prev parent reply other threads:[~2004-08-21 22:08 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 [this message]
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
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=200408211806.32566.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=levon@movementarian.org \
--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