From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Oprofilefs cant handle > 99 cpus
Date: Mon, 19 Apr 2004 12:06:03 +0200 [thread overview]
Message-ID: <20040419100603.GI12480@lug-owl.de> (raw)
In-Reply-To: <20040418110658.GC26086@krispykreme>
On Sun, 2004-04-18 21:06:58 +1000, Anton Blanchard <anton@samba.org>
wrote in message <20040418110658.GC26086@krispykreme>:
> Oprofilefs cant handle > 99 cpus. This should fix it.
Erm, on what hardware are you testing? Some large POWER5 machine?
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak!
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
prev parent reply other threads:[~2004-04-19 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 11:06 [PATCH] Oprofilefs cant handle > 99 cpus Anton Blanchard
2004-04-18 16:37 ` Philippe Elie
2004-04-19 10:06 ` Jan-Benedict Glaw [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=20040419100603.GI12480@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
/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