From: Esben Nielsen <esn@vestas.com>
To: linux-kernel@vger.kernel.org
Subject: Large IP packets over ArcNet (netif_wake_queue propagation)
Date: 29 Jan 2003 12:28:16 +0100 [thread overview]
Message-ID: <1043839696.21327.166.camel@tux> (raw)
Synopsis:
I am writing test-software for our ArcNet-driver for vxWorks. I use a
Linux machine running 2.4.18 as test-bench. I am trying to test our
rfc1201 (IP over ArcNet) implementation by ping'ing with large packets.
This fails:
Linux simply doesn't send all the IP-fragments.
I then went into the driver and increased the queue-length
from
dev->tx_queue_len = 40;
to
dev->tx_queue_len = 60;
and then it worked.
It seems to me the IP-layer is not notified when the device queue is
emptied by the device and thus doesn't send out the missing fragments.
I tried to look into the net core code to find out: Indeed I could not
find any notification to the higher level protocols.
In vxWorks I am used to waking the higher-level protocols directly
(there is no generic device-specific queue). Thus IP stack can continue
with the next IP-fragment right away. Apparently the Linux IP-stack
can't as it is not notified that the device is ready to send again.
I am really understanding this correctly???
Also, I want to run a raw packet protocol along with IP. That protocol
works best with a small queue - maximum 10 packets!
Esben Nielsen
Vestas Wind Systems
reply other threads:[~2003-01-29 11:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1043839696.21327.166.camel@tux \
--to=esn@vestas.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome