linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "aldo lab" <aldo.lab@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: Performance on PowerQuicc8280 linux based
Date: Wed, 15 Nov 2006 15:54:51 +0100	[thread overview]
Message-ID: <6e41d1460611150654j6e532ae1pbe378685539e257e@mail.gmail.com> (raw)

I've a system Linux based on ppc8280 platform with unstable
performance from a compiling to another.
I've a board with 2 Ethernet interfaces and I inject traffic in one of
this and analyze the number of packets that I receive in the other
one.
I obtained 60000 pkt/s the first time, the second time i recompiling
the kernel just changing some died function that is not involved in
the flow of the packet.In that case I obtained 47000 pkt/s and it
seems that moving code position change the behaviour in term of cache
functionality.
Could someone help me to understand this strange situation

Regards
Aldo

             reply	other threads:[~2006-11-15 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 14:54 aldo lab [this message]
2006-11-15 16:21 ` Performance on PowerQuicc8280 linux based Jeff Mock
2006-11-15 17:39   ` Dan Malek
2006-11-16  9:22     ` aldo lab

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=6e41d1460611150654j6e532ae1pbe378685539e257e@mail.gmail.com \
    --to=aldo.lab@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).