All of lore.kernel.org
 help / color / mirror / Atom feed
From: LEROY christophe <christophe.leroy@c-s.fr>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Huge performance degradation for UDP between 2.4.17 and 2.6
Date: Sun, 05 Aug 2012 10:16:05 +0200	[thread overview]
Message-ID: <501E2BC5.5020709@c-s.fr> (raw)
In-Reply-To: <1343916836.9299.189.camel@edumazet-glaptop>

Le 02/08/2012 16:13, Eric Dumazet a écrit :
> On Thu, 2012-08-02 at 14:27 +0200, 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 ?
> kernel size is probably too big for your old / slow cpu.
>
> Maybe you added too many features on your 3.4.7 kernel. (netfilter ?
> SLUB debugging ...)
>
> Its hard to say, 2.4.17 had less features and was faster.
>

Thanks for your answer.
Yes I have netfilter as I need it. However, I tried without it and still 
need about 37 seconds to send the 160000 packets I was sending in 11 
seconds with 2.4.17

I don't think there is any problem with size of the kernel. I still have 
plenty of memory available.

All debugging is turned off, and I'm not using SLUB but SLOB.
I have 32Mbytes of RAM. Would SLUB be more performant than SLOB ?

Christophe

  reply	other threads:[~2012-08-05  8:15 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 [this message]
2012-08-05  8:28     ` Eric Dumazet
2012-08-06  9:27       ` leroy christophe
2012-08-03  5:12 ` Chris Friesen

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=501E2BC5.5020709@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=eric.dumazet@gmail.com \
    --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.