From: Patrick McHardy <kaber@trash.net>
To: Krzysztof Oledzki <ole@ans.pl>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH] vlan: propogate MTU changes
Date: Tue, 07 Oct 2008 00:38:20 +0200 [thread overview]
Message-ID: <48EA935C.7090106@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0810062208370.6758@bizon.gios.gov.pl>
Krzysztof Oledzki wrote:
>
>
> On Mon, 6 Oct 2008, Stephen Hemminger wrote:
>
>> Propogate MTU changes of underlying device to all related VLAN
>> devices.
>> see: https://bugzilla.vyatta.com/show_bug.cgi?id=3742
>
> Not sure about this... Some switches (HP ProCurve for example) allow to
> select which vlan accepts jumbo frames and which does not and attach
> both to the same port. It is quite useful as you are able to setup one
> vlan with jumbo frames dedicated for example to servers connected by
> 1G/10G links, and a second vlan with standard 1500 MTU distributed to
> non jumbo-aware switches/workstations.
Thats why I favour the knob to specify the desired behaviour.
Treating a VLAN device as a seperate entity from the ethernet
device which just has the same hardware-imposed restrictions
seems like a valid view to me.
prev parent reply other threads:[~2008-10-06 22:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 15:30 [PATCH] vlan: propogate MTU changes Stephen Hemminger
2008-10-06 16:02 ` Patrick McHardy
2008-10-06 17:54 ` Stephen Hemminger
2008-10-06 18:25 ` [PATCH] vlan: propogate MTU changes (v2) Stephen Hemminger
2008-10-06 18:45 ` Duyck, Alexander H
2008-10-06 19:20 ` Ben Hutchings
2008-10-06 22:53 ` Patrick McHardy
2008-10-06 22:33 ` [PATCH] vlan: propogate MTU changes Patrick McHardy
2008-10-06 22:50 ` Rick Jones
2008-10-06 23:02 ` Patrick McHardy
2008-10-06 23:04 ` Patrick McHardy
2008-10-06 23:18 ` Rick Jones
2008-10-06 23:33 ` Patrick McHardy
2008-10-07 23:05 ` David Miller
2008-10-08 11:53 ` Patrick McHardy
2008-10-06 20:14 ` Krzysztof Oledzki
2008-10-06 22:38 ` Patrick McHardy [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=48EA935C.7090106@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=ole@ans.pl \
--cc=shemminger@vyatta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.