From: David Miller <davem@davemloft.net>
To: ebiederm@xmission.com
Cc: netdev@vger.kernel.org, containers@lists.osdl.org,
dlezcano@fr.ibm.com, xemul@openvz.org
Subject: Re: [PATCH] veth: Allow setting the L3 MTU
Date: Tue, 03 Mar 2009 23:36:16 -0800 (PST) [thread overview]
Message-ID: <20090303.233616.17571375.davem@davemloft.net> (raw)
In-Reply-To: <m1ab813ox1.fsf@fess.ebiederm.org>
From: ebiederm@xmission.com (Eric W. Biederman)
Date: Tue, 03 Mar 2009 20:14:18 -0800
> The limitation to only 1500 byte mtu's limits the utility of the veth
> device for testing routing. So implement implement a configurable
> MTU.
>
> For consistency I drop packets on the receive side when they are
> larger than the MTU. I count those drops. And I allow
> a little padding for vlan headers.
>
> I also test the mtu when a new device is created with netlink
> because that path currently bypasses the current mtu setting
> code.
>
> Signed-off-by: Eric Biederman <ebiederm@aristanetworks.com>
Applied to net-next-2.6, thanks Eric.
prev parent reply other threads:[~2009-03-04 7:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 4:14 [PATCH] veth: Allow setting the L3 MTU Eric W. Biederman
2009-03-04 7:36 ` 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=20090303.233616.17571375.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=containers@lists.osdl.org \
--cc=dlezcano@fr.ibm.com \
--cc=ebiederm@xmission.com \
--cc=netdev@vger.kernel.org \
--cc=xemul@openvz.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