From: David Miller <davem@davemloft.net>
To: horms@verge.net.au
Cc: mst@redhat.com, eric.dumazet@gmail.com, netdev@vger.kernel.org,
johann.baudy@gnu-log.net
Subject: Re: [PATCH] af_packet: account for VLAN when checking packet size
Date: Wed, 27 Oct 2010 08:48:54 -0700 (PDT) [thread overview]
Message-ID: <20101027.084854.71130929.davem@davemloft.net> (raw)
In-Reply-To: <20101022084052.GA2118@verge.net.au>
From: Simon Horman <horms@verge.net.au>
Date: Fri, 22 Oct 2010 10:41:26 +0200
> Incidently, I believe that this problem will only become more acute
> and complex if support for 802.1ad (Provider Bridges, aka Q-in-Q),
> 802.1ah (Provider Backbone Bridges, aka MAC-in-MAC) or other standards
> which further extend the maximum frame size.
No doubt.
> Dave, you were mentioning to me the other day that the kernel
> already supports some notion of Q-in-Q (though its not 802.1ad).
> Does the current implementation allow for frames > 1504 bytes?
It's only going to hardware offload and allow the extra space
for the outer-most VLAN tag. Everthing inside of the outer
tag will be handled in software as far as Linux is concerned.
> Is that a complication to the change proposed here?
For now, I don't think so.
prev parent reply other threads:[~2010-10-27 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 19:24 sending VLAN packets via packet_mmap Phil Sutter
2010-10-07 6:53 ` David Miller
2010-10-11 13:15 ` Phil Sutter
2010-10-11 13:25 ` [PATCH] af_packet: account for VLAN when checking packet size Phil Sutter
2010-10-11 14:03 ` Eric Dumazet
2010-10-11 16:01 ` David Miller
2010-10-11 17:29 ` Phil Sutter
2010-10-12 17:19 ` Michael S. Tsirkin
2010-10-12 17:40 ` David Miller
2010-10-22 8:41 ` Simon Horman
2010-10-27 15:48 ` David Miller [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=20101027.084854.71130929.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=horms@verge.net.au \
--cc=johann.baudy@gnu-log.net \
--cc=mst@redhat.com \
--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).