Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@mips.com>
To: <hadi@cyberus.ca>, <linux-mips@linux-mips.org>
Cc: <sibyte-users@bitmover.com>
Subject: Re: weird sb1250 behavior
Date: Fri, 28 May 2004 22:11:49 +0200	[thread overview]
Message-ID: <01ea01c444f0$03d6b8e0$10eca8c0@grendel> (raw)
In-Reply-To: 1085773008.1029.59.camel@jzny.localdomain

This could be any one of a number of wierd effects that one sees
from time to time.  Rather than speculate, would it be too much
to ask you to run objdump --disassemble on the different versions
of your test program and post the results?

----- Original Message ----- 
From: "jamal" <hadi@cyberus.ca>
To: <linux-mips@linux-mips.org>
Cc: <sibyte-users@bitmover.com>
Sent: Friday, May 28, 2004 21:36
Subject: weird sb1250 behavior


> 
> found some very strange behavior with sb1250.
> Gcc 3.2.3 with sibyte mods. Running Linux 2.4.21 with whatever
> mods off sibyte.
> 
> Testcase:
> sending a large amount of traffic 
> -->eth0-->someprocessing-->eth1
> 
> given the nature of processing, say i was getting 100Kpps throughput.
> Now i fire a very basic program that has just loops and forever
> sums up two numbers.
> 
> ---
>       1 #include <stdlib.h>
>       2 
>       3 int main ()
>       4 {
>       5         int a = 1;
>       6         int b = 2;
>       7         int c = 0; 
>       8         // int c;
>       9         while (1) {
>      10                 c = a + b;
>      11         }
>      12 }
> --------
> 
> I see very little drop in throughput - probably around 0.01%.
> 
> Now comment line 7 then uncomment line 8. Hallelujah.
> Perfomance drops to about 100pps. Thats about a factor of 1000 down!
> 
> Interesting thing is if you add a nop (__asm__ __volatile__("nop");)
> in the second version just before the while loop, we get back the same
> performance as in the earlier version.
> Apologies in advance for attaching objdumps (since there maybe folks who
> dont have access to the sibyte tools)
> 1) while-init-dis is for case 1 where c is initialized
> 2) while-noinit-dis is for case 2 where c is not initialize
> 3) while-nop-dis is for case 3 when you have nop thrown in.
> 
> 
> cheers,
> jamal
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: "Kevin D. Kissell" <kevink@mips.com>
To: hadi@cyberus.ca, linux-mips@linux-mips.org
Cc: sibyte-users@bitmover.com
Subject: Re: weird sb1250 behavior
Date: Fri, 28 May 2004 22:11:49 +0200	[thread overview]
Message-ID: <01ea01c444f0$03d6b8e0$10eca8c0@grendel> (raw)
Message-ID: <20040528201149.pwDXiZ-jEB45L7ZGwIpN6kWgWkGhsyqa4L_1-JOD7_Y@z> (raw)
In-Reply-To: 1085773008.1029.59.camel@jzny.localdomain

This could be any one of a number of wierd effects that one sees
from time to time.  Rather than speculate, would it be too much
to ask you to run objdump --disassemble on the different versions
of your test program and post the results?

----- Original Message ----- 
From: "jamal" <hadi@cyberus.ca>
To: <linux-mips@linux-mips.org>
Cc: <sibyte-users@bitmover.com>
Sent: Friday, May 28, 2004 21:36
Subject: weird sb1250 behavior


> 
> found some very strange behavior with sb1250.
> Gcc 3.2.3 with sibyte mods. Running Linux 2.4.21 with whatever
> mods off sibyte.
> 
> Testcase:
> sending a large amount of traffic 
> -->eth0-->someprocessing-->eth1
> 
> given the nature of processing, say i was getting 100Kpps throughput.
> Now i fire a very basic program that has just loops and forever
> sums up two numbers.
> 
> ---
>       1 #include <stdlib.h>
>       2 
>       3 int main ()
>       4 {
>       5         int a = 1;
>       6         int b = 2;
>       7         int c = 0; 
>       8         // int c;
>       9         while (1) {
>      10                 c = a + b;
>      11         }
>      12 }
> --------
> 
> I see very little drop in throughput - probably around 0.01%.
> 
> Now comment line 7 then uncomment line 8. Hallelujah.
> Perfomance drops to about 100pps. Thats about a factor of 1000 down!
> 
> Interesting thing is if you add a nop (__asm__ __volatile__("nop");)
> in the second version just before the while loop, we get back the same
> performance as in the earlier version.
> Apologies in advance for attaching objdumps (since there maybe folks who
> dont have access to the sibyte tools)
> 1) while-init-dis is for case 1 where c is initialized
> 2) while-noinit-dis is for case 2 where c is not initialize
> 3) while-nop-dis is for case 3 when you have nop thrown in.
> 
> 
> cheers,
> jamal
> 
> 

  reply	other threads:[~2004-05-28 20:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-28 19:36 weird sb1250 behavior jamal
2004-05-28 20:11 ` Kevin D. Kissell [this message]
2004-05-28 20:11   ` Kevin D. Kissell
2004-05-28 20:15   ` jamal
  -- strict thread matches above, loose matches on Subject: below --
2004-05-28 20:11 Adam Kiepul

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='01ea01c444f0$03d6b8e0$10eca8c0@grendel' \
    --to=kevink@mips.com \
    --cc=hadi@cyberus.ca \
    --cc=linux-mips@linux-mips.org \
    --cc=sibyte-users@bitmover.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