mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Levon <levon@movementarian.org>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: Andrew Morton <akpm@osdl.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: Sun, 22 Aug 2004 00:14:38 +0100	[thread overview]
Message-ID: <20040821231437.GB20175@compsoc.man.ac.uk> (raw)
In-Reply-To: <200408211806.32566.jbarnes@sgi.com>

On Sat, Aug 21, 2004 at 06:06:31PM -0400, Jesse Barnes wrote:

> 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).

That must be profile_rwsem in kernel/profile.c since the rest of the
code won't be doing anything. I imagine it needs RCUing.

> 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?

No idea, I don't have time to track what Red Hat do or don't use. I
recommend oprofile CVS or the last release.

john

  reply	other threads:[~2004-08-21 23:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-21 19:26 John Levon
2004-08-21 20:58 ` Andrew Morton
2004-08-21 22:06   ` Jesse Barnes
2004-08-21 23:14     ` John Levon [this message]
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=20040821231437.GB20175@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

Powered by JetHome