From: P@draigBrady.com
To: Oded Comay <comay@pod.tau.ac.il>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is PACKET_RX_RING broken in 2.6.0-test?
Date: Mon, 24 Nov 2003 10:28:21 +0000 [thread overview]
Message-ID: <3FC1DD45.9070107@draigBrady.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0311222158400.9419-200000@pod.tau.ac.il>
Oded Comay wrote:
> The PACKET_RX_RING mechanism (enabled by CONFIG_PACKET_MMAP) appears to be
> somewhat broken in 2.6.0-test* (2.6 for short). There are 3 issues:
>
> 1. Performance in 2.6 is much lower than in 2.4. As an example, using the
> same hardware and under the same traffic load, the attached sample program
> could process 177K packets/sec in 2.4, but only 70K packets/sec in 2.6.
I'm guessing the scheduling changes are the cause?
Try messing with sched_setscheduler (like:
http://awgn.antifork.org/codes/brute.c)
Anyone else notice that the packet buffer messes up if
packets are being received while it's being created.
I worked around it here by bringing the interfaces
up AFTER the buffer is created.
Pádraig.
next prev parent reply other threads:[~2003-11-24 10:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 20:02 Is PACKET_RX_RING broken in 2.6.0-test? Oded Comay
2003-11-24 10:28 ` P [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-22 20:48 Oded Comay
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=3FC1DD45.9070107@draigBrady.com \
--to=p@draigbrady.com \
--cc=comay@pod.tau.ac.il \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox