From: "Olivier Crameri" <olivier.crameri@gmail.com>
To: netdev@vger.kernel.org
Cc: "Yoshio Turner" <yoshiotu@hpl.hp.com>,
"Santos, Jose Renato G" <joserenato.santos@hp.com>,
"Janakiraman, John" <john.janakiraman@hp.com>
Subject: Offloading features in VLAN interfaces
Date: Fri, 29 Sep 2006 17:21:44 -0700 [thread overview]
Message-ID: <b54af0b00609291721u16acb2f1ma918adec9b2e782b@mail.gmail.com> (raw)
Hi,
after running some experiments, we realised that using VLAN support in
Linux caused some overhead. It turned out to be that the offloading
features of our NIC (tso, sg, checksum offloading) were not beeing
used.
After digging a little bit in the code, we realised that the VLAN code
did not set the features parameter of the net_device structure for the
virtual interface. Attached is a patch with a suggested solution to
this problem.
Please let us know if this is an acceptable patch.
Thanks,
Olivier Crameri, HP Labs
next reply other threads:[~2006-09-30 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-30 0:21 Olivier Crameri [this message]
2006-09-30 0:25 ` Offloading features in VLAN interfaces Olivier Crameri
2006-09-30 3:33 ` Stephen Hemminger
2006-10-05 16:25 ` Ben Greear
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=b54af0b00609291721u16acb2f1ma918adec9b2e782b@mail.gmail.com \
--to=olivier.crameri@gmail.com \
--cc=john.janakiraman@hp.com \
--cc=joserenato.santos@hp.com \
--cc=netdev@vger.kernel.org \
--cc=olivier.crameri@epfl.ch \
--cc=yoshiotu@hpl.hp.com \
/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).