From: Or Gerlitz <ogerlitz@Voltaire.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: difference in counters values between vlan and parent device
Date: Mon, 29 Jun 2009 18:05:06 +0300 [thread overview]
Message-ID: <4A48D822.6020100@Voltaire.com> (raw)
In-Reply-To: <4A48D191.9020903@trash.net>
Patrick McHardy wrote:
> So the average packet size is 56 bytes on eth1 and 42 bytes
> on eth1.4001. So the difference is 14 bytes, which is expected
> since the mac header is pulled off before delivery to the VLAN device.
yes makes sense... I am using 22 bytes for netperf payload which without VLAN produces 64=22+8+20+14 bytes frames (8 bytes for UDP header, 20 bytes for IP header, 14 bytes for Eth header). Now with vlans, how many bytes are on the wire, 78=64+14 ?
Or.
prev parent reply other threads:[~2009-06-29 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 14:16 difference in counters values between vlan and parent device Or Gerlitz
2009-06-29 14:37 ` Patrick McHardy
2009-06-29 15:05 ` Or Gerlitz [this message]
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=4A48D822.6020100@Voltaire.com \
--to=ogerlitz@voltaire.com \
--cc=kaber@trash.net \
--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).