From: Ichiro Suzuki <isuzuki@miraclelinux.com>
To: netdev@vger.kernel.org
Cc: Naohiro Ooiwa <nooiwa@miraclelinux.com>
Subject: Question about VLAN + checksum offloading
Date: Fri, 16 May 2008 16:52:54 +0900 [thread overview]
Message-ID: <1210924374.5136.94.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
Hi,
Looking in oprofile log, I observed
csum_partial_copy_generic()
is invoked for a 802.1Q VLAN device created on e1000,
This suggests checksum offloading is not in effect.
The offloading works fine when e1000 is used directly.
Attached one liner patch fixes this. But, it seems
too obvious to be a correct answer.
My questions are,
o Is it right to expect checksum offloading should work
on VLAN devices?
o If so, is there any mechanism to propagate
real_dev->features flags in vlan.c?
o If such mechanism doesn't exist, is my patch reasonable?
.
The machine arch is x86_64. I got similar results
on an ancient 2.6.9 kernel and on the latest 2.6.25.
Thanks in advance,
----------------------------------------------
Ichiro Suzuki <isuzuki@miraclelinux.com>
Miracle Linux Corp., Advanced Technology Group
----------------------------------------------
[-- Attachment #2: linux-2.6.25_vlan.patch --]
[-- Type: text/x-patch, Size: 476 bytes --]
--- linux-2.6.25.orig/net/8021q/vlan.c 2008-04-17 11:49:44.000000000 +0900
+++ linux-2.6.25/net/8021q/vlan.c 2008-05-16 15:03:03.000000000 +0900
@@ -333,6 +333,9 @@ static int register_vlan_device(struct n
*/
new_dev->mtu = real_dev->mtu;
+ /* features setting */
+ new_dev->features = real_dev->features;
+
vlan_dev_info(new_dev)->vlan_id = VLAN_ID; /* 1 through VLAN_VID_MASK */
vlan_dev_info(new_dev)->real_dev = real_dev;
vlan_dev_info(new_dev)->dent = NULL;
next reply other threads:[~2008-05-16 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 7:52 Ichiro Suzuki [this message]
2008-05-19 17:36 ` Question about VLAN + checksum offloading Waskiewicz Jr, Peter P
2008-05-19 17:43 ` Patrick McHardy
2008-05-19 17:45 ` Patrick McHardy
2008-05-20 3:19 ` Ichiro Suzuki
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=1210924374.5136.94.camel@localhost.localdomain \
--to=isuzuki@miraclelinux.com \
--cc=netdev@vger.kernel.org \
--cc=nooiwa@miraclelinux.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).