All of lore.kernel.org
 help / color / mirror / Atom feed
From: "P.O. Gaillard" <pierre-olivier.gaillard@fr.thalesgroup.com>
To: linux-kernel@vger.kernel.org
Subject: voluntary-preempt-2.6.8.1-P1 seems to lose UDP messages.
Date: Wed, 18 Aug 2004 13:10:27 +0200	[thread overview]
Message-ID: <41233923.80202@fr.thalesgroup.com> (raw)

Hello,

I have a real-time application that transmits 20 MBytes/s over UDP/Gigabit 
Ethernet between 2 PCs. The NICs are from Intel and use the e1000 driver 
(MTU=1500). On the receive side, the computer has to process the data (real-time 
tasks doing signal processing work and using up 50% of the CPU time).

This app works OK with 2.6.7 and 2.6.8.1 : the app does not complain about lost 
messages.

But when I use the voluntary-preemt-2.6.8.1-P1 patch on the receiving PC, the 
app starts complaining about lost messages. And also, netstat -s -u shows that 
lots of UDP packets are lost (on the PC that receives the data).
[root@centaurus root]# netstat -u -s
Udp:
     8433 packets received
     0 packets to unknown port received.
     869 packet receive errors
     366 packets sent

I have already retried with the e1000 parameters RxIntDelay=0 and 
RxDescriptors=1024. This did not improve anything.

Note: I don't see any error message with dmesg nor in /var/log/messages.

I find the voluntary-preempt series very important and would really like it to 
make its way into the stock kernel. I would therefore gladly make additional 
tests to help you find the problem. Please give me directions.


	thanks for your help,

	P.O. Gaillard



             reply	other threads:[~2004-08-18 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 11:10 P.O. Gaillard [this message]
2004-08-18 18:31 ` voluntary-preempt-2.6.8.1-P1 seems to lose UDP messages Lee Revell
2004-08-19  7:25 ` P.O. Gaillard

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=41233923.80202@fr.thalesgroup.com \
    --to=pierre-olivier.gaillard@fr.thalesgroup.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.