From: gshan <gshan@alcatel-lucent.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Big sized packets have been dropped strangly
Date: Wed, 04 Jul 2007 17:11:09 +0800 [thread overview]
Message-ID: <468B642D.9030109@alcatel-lucent.com> (raw)
Hey Guys,
I got a strange problem recently but no ideas, so to post the question
here. We have a FPGA what finish ATM AAL5 to ethernet frame, and CPU
receives IP packets from it. The interface based on the FPGA (called
sar0) has been bound with several IP addresses. When the MTU of the
interface is configurated to 1500, trivial packets can be received, but
big-sized packets are dropped. If the MTU is increased to 9500,
everything is ok except the NFS connection. We mounted with another
machine through sar0. When the MTU is 9500, the speed of the NFS becomes
very very slow (it almost took 10 minutes to transfer 100KB files).
I don't know why it is and how to solve it. Any suggestions are appreciated!
Thanks,
Gavin
next reply other threads:[~2007-07-04 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 9:11 gshan [this message]
2007-07-05 22:01 ` Big sized packets have been dropped strangly Bill Davidsen
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=468B642D.9030109@alcatel-lucent.com \
--to=gshan@alcatel-lucent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).