Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Jun Sun <jsun@mvista.com>
To: Johannes Stezenbach <js@convergence.de>
Cc: "Kevin D. Kissell" <kevink@mips.com>, linux-mips@oss.sgi.com
Subject: Re: LL/SC benchmarking [was: Mipsel libc with LL/SC online anywhere?]
Date: Thu, 25 Jul 2002 10:06:55 -0700	[thread overview]
Message-ID: <3D40302F.40806@mvista.com> (raw)
In-Reply-To: 20020725162539.GA8804@convergence.de

Johannes Stezenbach wrote:
> On Fri, Jul 19, 2002 at 02:38:29PM +0200, Johannes Stezenbach wrote:
> 
>>On Fri, Jul 12, 2002 at 03:04:07PM +0200, Kevin D. Kissell wrote:
>>
>>>I'm benchmarking some code that does lots of
>>>semaphores, and with the libc from the "standard"
>>>MIPS/SGI RH 7.1 distribution, those are done using
>>>sysmips, in the interest of universality.
>>
>>I'm working on a platform without LL/SC, an embedded system/SOC
>>with a NEC VR4120A CPU core. To find out the effect of sysmips
>>vs. emulated LL/SC vs. the branch-likely trick posted by
>>Kevin D. Kissell <kevink@mips.com> on Tue, 22 Jan 2002 18:16:25 +0100
>>I created an experimental patch for glibc-2.2.5 which allows
>>run-time switching of the _test_and_set() and __compare_and_swap()
>>implementation based on the presence of two "switch files" in /etc/.
> 
> ... 
> 
>>For lack of a better benchmark I used some of the examples from
>>glibc-2.2.5/linuxthreads/Examples. The numbers are from the third
>>of three successive runs of 'time exN >/dev/null'.
> 
> 
> I did some more benchmarking with a test application based on
> gtk+-directfb (http://directfb.org/). The benchmark does not
> include GUI stuff, but rather reading of lots of external data
> into internal data structures (which are GLib-2.0 GObjects).
> The test application has three threads, but nearly all processing
> is done in the main thread.
> 
> I think that the numbers are meaningful for our type of application.
> 
> sysmips:
>         real    1m19.358s
>         user    0m28.150s
>         sys     0m47.250s
> 
> LL/SC emulation:
>         real    0m41.246s
>         user    0m25.390s
>         sys     0m12.240s
> 
> branch-likely hack (hm, still without kernel patch...):
>         real    0m25.126s
>         user    0m17.240s
>         sys     0m2.310s

Johannes,

This is great stuff!  Can you explain what are "real", "user", and "sys"? 
Also, what is your initial conclusion?

Jun

  reply	other threads:[~2002-07-25 17:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12 13:04 Mipsel libc with LL/SC online anywhere? Kevin D. Kissell
2002-07-12 13:04 ` Kevin D. Kissell
2002-07-19 12:38 ` LL/SC benchmarking [was: Mipsel libc with LL/SC online anywhere?] Johannes Stezenbach
2002-07-19 15:54   ` Richard Hodges
2002-07-22 10:35     ` Johannes Stezenbach
2002-07-25 16:25   ` Johannes Stezenbach
2002-07-25 17:06     ` Jun Sun [this message]
2002-07-25 18:45       ` Johannes Stezenbach
2002-07-25 18:56         ` Jun Sun
2002-07-25 19:24           ` Johannes Stezenbach
2002-07-25 21:49         ` Kevin D. Kissell
2002-07-26 19:35           ` Kevin D. Kissell

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=3D40302F.40806@mvista.com \
    --to=jsun@mvista.com \
    --cc=js@convergence.de \
    --cc=kevink@mips.com \
    --cc=linux-mips@oss.sgi.com \
    /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