From: Emil Micek <emil.micek@tkrjasek.cz>
To: netdev@vger.kernel.org
Subject: change the way e1000 is handling short VLAN frames
Date: Fri, 21 Sep 2007 09:31:45 +0200 [thread overview]
Message-ID: <1190359905.3551.28.camel@magi.nadr> (raw)
Hello list,
I'd like to change behaviour of e1000 module when transmiting short
ethernet frames (shorter then 64 bytes) trough VLAN interface.
Current e1000 (according to our observations) first appends 4 bytes of
VLAN tag and then pads the frame to 64 bytes with zeroes if necessary
before transmiting it.
I'd like to change it so it first pads the frame to 64 B and appends the
VLAN tag afterwards, so the resulting VLAN frame would be 68 bytes
minimum.
I want to do it because C3 CMTS from arris, which is connected to our
linux box, has problems handling VLAN frames shorter then 68 bytes.
As i'm quite a newbie concerning linux sources and c programing, i'd
like to ask you if this'd be trivial or complex change and if someone
can point out relevant portions of the sources, where the necessary
changes should be done.
Regards
Emil Micek
next reply other threads:[~2007-09-21 8:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-21 7:31 Emil Micek [this message]
2007-09-21 11:59 ` change the way e1000 is handling short VLAN frames jamal
2007-09-21 12:50 ` Emil Micek
2007-09-21 13:37 ` jamal
2007-09-21 13:46 ` jamal
2007-09-21 14:27 ` Francesco Fondelli
2007-09-21 15:43 ` Ben Greear
2007-09-21 21:12 ` jamal
2007-09-21 21:18 ` Ben Greear
2007-09-21 21:21 ` Kok, Auke
2007-09-21 21:29 ` jamal
2007-09-21 21:34 ` Kok, Auke
2007-09-21 21:43 ` jamal
2007-09-21 22:02 ` Chris Leech
2007-09-24 8:40 ` Emil Micek
2007-09-21 21:27 ` Chris Leech
2007-09-21 21:36 ` jamal
2007-09-21 17:05 ` Brandeburg, Jesse
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=1190359905.3551.28.camel@magi.nadr \
--to=emil.micek@tkrjasek.cz \
--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).