From: P@draigBrady.com
To: hadi@cyberus.ca
Cc: Karsten Desler <kdesler@soohrt.org>,
Robert Olsson <Robert.Olsson@data.slu.se>,
"David S. Miller" <davem@davemloft.net>,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: _High_ CPU usage while routing (mostly) small UDP packets
Date: Tue, 07 Dec 2004 13:39:14 +0000 [thread overview]
Message-ID: <41B5B282.9040909@draigBrady.com> (raw)
In-Reply-To: <1102424673.1093.124.camel@jzny.localdomain>
jamal wrote:
> On Tue, 2004-12-07 at 07:50, Karsten Desler wrote:
>
>
>>Currently I'm having problems capturing packets with tcpdump (lots of
>>"packets dropped by kernel") which indicates to me that there's
>>genuinely not much (enough) idle time sitting around.
>>
>
> Ah, more hints. So you are not trying to forward - rather just packet
> capturing?
> Are you using a tcpdump patched with mmaped packet socket?
>
> The 230-240Kpps you are reporting as a capture dont seem as unreasonable
> as i thought then. Neither would the CPU use.
Yes this is vital Karsten, otherwise tcpdump
will do 2 syscalls per packet, which is the
bottleneck in my experience.
You may want to try a simpler capture program that
uses the kernel PACKET_MMAP feature directly:
http://www.scaramanga.co.uk/code-fu/lincap.c
--
Pádraig Brady - http://www.pixelbeat.org
--
next prev parent reply other threads:[~2004-12-07 13:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 20:53 _High_ CPU usage while routing (mostly) small UDP packets Karsten Desler
2004-12-06 21:48 ` David S. Miller
2004-12-06 22:41 ` Karsten Desler
2004-12-06 23:53 ` Bernd Eckenfels
2004-12-07 0:20 ` Karsten Desler
2004-12-07 2:46 ` jamal
2004-12-07 2:54 ` Karsten Desler
2004-12-07 3:18 ` jamal
2004-12-07 3:24 ` Karsten Desler
2004-12-07 3:30 ` jamal
2004-12-07 4:02 ` Karsten Desler
2004-12-07 10:21 ` Karsten Desler
2004-12-07 12:34 ` jamal
2004-12-07 13:14 ` Karsten Desler
2004-12-06 23:56 ` Con Kolivas
2004-12-07 0:18 ` Karsten Desler
2004-12-07 10:47 ` P
2004-12-07 11:21 ` Karsten Desler
2004-12-07 12:38 ` Robert Olsson
2004-12-07 12:50 ` Karsten Desler
2004-12-07 13:04 ` jamal
2004-12-07 13:11 ` Karsten Desler
2004-12-07 13:39 ` P [this message]
2004-12-07 18:38 ` Karsten Desler
2004-12-08 5:39 ` Willy Tarreau
2004-12-08 13:08 ` Karsten Desler
2004-12-08 13:27 ` jamal
2004-12-07 21:10 ` Karsten Desler
2004-12-07 22:40 ` Robert Olsson
2004-12-08 22:06 ` Karsten Desler
2004-12-08 4:31 ` jamal
2004-12-08 13:26 ` Karsten Desler
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=41B5B282.9040909@draigBrady.com \
--to=p@draigbrady.com \
--cc=Robert.Olsson@data.slu.se \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kdesler@soohrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 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.