From: FASSINO Jean-Philippe <jeanphilippe.fassino@cnet.francetelecom.fr>
To: Paul Mackerras <paulus@linuxcare.com>
Cc: "linuxppc-dev@lists.linuxppc.org"
<linuxppc-dev@lists.linuxppc.org>,
Benjamin Herrenschmidt <bh40@calva.net>,
Gabriel Paubert <paubert@iram.es>
Subject: Re: Patch for optimize context switch
Date: Tue, 22 Feb 2000 12:23:46 +0100 [thread overview]
Message-ID: <38B271C2.FE9C38C2@cnet.francetelecom.fr> (raw)
In-Reply-To: 38B25749.2C4B0E1A@cnet.francetelecom.fr
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
FASSINO Jean-Philippe wrote:
> Paul Mackerras wrote:
>
> > Interesting. How much does it reduce the context switch time? Did you
> > run lmbench or something to see if it makes it go faster?
I have got result of lmbench for Context switching (initlevel 1).
I'm running 5 bench with and without patch on a PBG3/400.
Result is in attach. The average is :
Context switching - times in microseconds - smaller is better
-------------------------------------------------------------
Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw
--------- ------------- ----- ------ ------ ------ ------ ------- -------
With patch. ======
ppc-linux Linux 2.2.15p 0.6 8 91 26 117 28 239
Without patch ======
ppc-linux Linux 2.2.15p 1 7 102 26 121 28 240
What do you think about this result ???
I'm thinking to say something it is necessary to do many bench run !
Here, performance vary too much between two run to really say something.
Jean-Philippe
--
--------------------------------------------------------------------------
Jean-Philippe FASSINO Tel : 04 76 76 45 52
CNET : DTL/ASR mailto:jeanphilippe.fassino@cnet.francetelecom.fr
--------------------------------------------------------------------------
[-- Attachment #2: res.txt --]
[-- Type: text/plain, Size: 1065 bytes --]
Context switching - times in microseconds - smaller is better
-------------------------------------------------------------
Host OS 2p/0K 2p/16K 2p/64K 8p/16K 8p/64K 16p/16K 16p/64K
ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw ctxsw
--------- ------------- ----- ------ ------ ------ ------ ------- -------
ppc-linux Linux 2.2.15p 1 7 90 26 107 31 222
ppc-linux Linux 2.2.15p 1 7 91 26 110 29 257
ppc-linux Linux 2.2.15p 1 7 90 25 112 26 233
ppc-linux Linux 2.2.15p 1 7 92 25 126 27 243
ppc-linux Linux 2.2.15p 1 7 147 26 150 27 245
ppc-linux Linux 2.2.15p 0 7 92 25 136 28 270
ppc-linux Linux 2.2.15p 1 8 90 27 103 27 211
ppc-linux Linux 2.2.15p 0 9 90 30 112 32 228
ppc-linux Linux 2.2.15p 1 7 91 25 130 29 277
ppc-linux Linux 2.2.15p 1 7 90 25 105 26 211
next prev parent reply other threads:[~2000-02-22 11:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-21 10:49 Patch for optimize context switch FASSINO Jean-Philippe
2000-02-21 23:12 ` Paul Mackerras
2000-02-22 9:27 ` Gabriel Paubert
2000-02-22 10:50 ` Benjamin Herrenschmidt
2000-02-22 11:13 ` Gabriel Paubert
2000-02-22 9:30 ` FASSINO Jean-Philippe
2000-02-22 11:23 ` FASSINO Jean-Philippe [this message]
2000-02-22 11:33 ` FASSINO Jean-Philippe
2000-02-22 11:50 ` Gabriel Paubert
2000-02-22 11:40 ` Gabriel Paubert
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=38B271C2.FE9C38C2@cnet.francetelecom.fr \
--to=jeanphilippe.fassino@cnet.francetelecom.fr \
--cc=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=paulus@linuxcare.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;
as well as URLs for NNTP newsgroup(s).