From: David Miller <davem@davemloft.net>
To: i.matveychikov@securitycode.ru
Cc: matvejchikov@gmail.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH] veth: keep peers MTU values synchronized
Date: Fri, 04 Apr 2014 10:49:21 -0400 (EDT) [thread overview]
Message-ID: <20140404.104921.1668611243816621886.davem@davemloft.net> (raw)
In-Reply-To: <533EC4D5.50304@securitycode.ru>
From: "Ilya V. Matveychikov" <i.matveychikov@securitycode.ru>
Date: Fri, 4 Apr 2014 18:42:29 +0400
> Peers are created at once and ether_setup used for the configuration so MTU
> values equals.
If an IFLA_MTU value is specified for the peer it will be honored.
next prev parent reply other threads:[~2014-04-04 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 21:33 [RFC PATCH] veth: keep peers MTU values synchronized Ilya V. Matveychikov
2014-04-04 14:25 ` David Miller
2014-04-04 14:42 ` Ilya V. Matveychikov
2014-04-04 14:49 ` David Miller [this message]
2014-04-04 15:04 ` Ilya V. Matveychikov
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=20140404.104921.1668611243816621886.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=i.matveychikov@securitycode.ru \
--cc=matvejchikov@gmail.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).