From: Chris Friesen <chris.friesen@genband.com>
To: leroy christophe <christophe.leroy@c-s.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Huge performance degradation for UDP between 2.4.17 and 2.6
Date: Thu, 02 Aug 2012 23:12:12 -0600 [thread overview]
Message-ID: <501B5DAC.7070400@genband.com> (raw)
In-Reply-To: <501A722D.1070900@c-s.fr>
On 08/02/2012 06:27 AM, leroy christophe wrote:
> Hi
>
> I'm having a big issue with UDP. Using a powerpc board (MPC860).
>
> With our board running kernel 2.4.17, I'm able to send 160000 voice
> packets (UDP, 96 bytes per packet) in 11 seconds.
> With the same board running either Kernel 2.6.35.14 or Kernel 3.4.7, I
> need 55 seconds to send the same amount of packets.
>
>
> Is there anything to tune in order to get same output rate as with
> Kernel 2.4 ?
Have you tried profiling it to see where the time is being spent? Also
turning off any unnecessary features, debugging, etc?
Chris
prev parent reply other threads:[~2012-08-03 5:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 12:27 Huge performance degradation for UDP between 2.4.17 and 2.6 leroy christophe
2012-08-02 14:13 ` Eric Dumazet
2012-08-05 8:16 ` LEROY christophe
2012-08-05 8:28 ` Eric Dumazet
2012-08-06 9:27 ` leroy christophe
2012-08-03 5:12 ` Chris Friesen [this message]
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=501B5DAC.7070400@genband.com \
--to=chris.friesen@genband.com \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.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.