All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Karl-Johan Karlsson <creideiki+linux-mips@ferretporn.se>
Cc: linux-mips@linux-mips.org
Subject: Re: Extreme system overhead on large IP27
Date: Mon, 23 Oct 2006 00:23:16 +0100	[thread overview]
Message-ID: <20061022232316.GA19127@linux-mips.org> (raw)
In-Reply-To: <20061022152158.GB17776@linux-mips.org>

On Sun, Oct 22, 2006 at 04:21:58PM +0100, Ralf Baechle wrote:

> > I have an Origin 2000 with 16 R12000 and 16 R10000 CPU:s, running a git 
> > snapshot kernel from 20060618 based on 2.6.17.10 (the latest available in 
> > Gentoo). Light loads run without problems, but as soon as the load average 
> > goes above 4-5 system overhead skyrockets and almost no useful work is being 
> > done (see top output below). OProfile is no help, since the daemon just 
> > throws away everything the kernel gives it (see output from strace of 
> > oprofiled below).
> > 
> > Does anyone know where this overhead is coming from, or how to get some data 
> > from OProfile so I can search for it myself? I'll try booting just the R12000 
> > part sometime soon to see if that helps with either problem.
> 
> Oprofile is a bit of a bitch on mixed processor systems since it assumes
> all processors to have identical performance counters.  However SGI in
> it's wisdem decieded the R12000 had to be better than the R10000 and
> changed it.  It is possible to work around that but lacking any mixed
> CPU configuration I've never done that.
> 
> With those annotations, the kernel part of oprofile doesn't yet support
> R1x000 processors, I'll try to cook up something.  Should be easy enough
> since the interface is nearly identical to MIPS32/MIPS64.

Okay, turns out as I suspected one of the well facts well disguised by the
R10000, MIPS32 and MIPS64 architecture manuals is that the R10000 MFPS,
MFPC, MTPS, MTPC instructions use the same encoding as MIPS32/MIPS64 mfc0
instructions with a selector argument,  So getting oprofile to actually
work on the R10000 family won't be hard.

  Ralf

  reply	other threads:[~2006-10-22 23:22 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21 19:59 Extreme system overhead on large IP27 Karl-Johan Karlsson
2006-10-22 15:21 ` Ralf Baechle
2006-10-22 23:23   ` Ralf Baechle [this message]
2006-10-23  0:19     ` Ralf Baechle
2006-10-23 21:30       ` Karl-Johan Karlsson
     [not found]         ` <20061023224318.GA1732@linux-mips.org>
2006-10-24 13:53           ` Karl-Johan Karlsson
2006-10-24 14:06             ` Ralf Baechle
2006-10-24 15:33               ` Ilya A. Volynets-Evenbakh
2006-10-24 15:44               ` Karl-Johan Karlsson
2006-10-24 15:50                 ` Ralf Baechle
2006-10-24 17:34                 ` Atsushi Nemoto
2006-10-24 17:50                   ` Ralf Baechle
2006-10-25  8:45                 ` Atsushi Nemoto
2006-10-26  4:05                   ` Atsushi Nemoto
2006-10-26  7:42                     ` Manish Lachwani
2006-10-26 14:16                       ` Atsushi Nemoto
2006-10-27  1:55                         ` mlachwani
2006-10-26  8:41                     ` Karl-Johan Karlsson
2006-10-26 12:56                     ` Ralf Baechle
2006-10-26 13:51                       ` Kevin D. Kissell
2006-10-26 13:51                         ` Kevin D. Kissell
2006-10-26 16:50                         ` Ralf Baechle

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=20061022232316.GA19127@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=creideiki+linux-mips@ferretporn.se \
    --cc=linux-mips@linux-mips.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 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.