From: "Ilya V. Matveychikov" <i.matveychikov@securitycode.ru>
To: David Miller <davem@davemloft.net>
Cc: <matvejchikov@gmail.com>, <netdev@vger.kernel.org>
Subject: Re: [RFC PATCH] veth: keep peers MTU values synchronized
Date: Fri, 4 Apr 2014 19:04:51 +0400 [thread overview]
Message-ID: <533ECA13.60305@securitycode.ru> (raw)
In-Reply-To: <20140404.104921.1668611243816621886.davem@davemloft.net>
On 04.04.2014 18:49, David Miller wrote:
> 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.
>
>
OK, I see it. Does that mean that the patch needs to be updated or the proposed
behavior is incorrect and must not be in kernel?
prev parent reply other threads:[~2014-04-04 15:04 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
2014-04-04 15:04 ` Ilya V. Matveychikov [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=533ECA13.60305@securitycode.ru \
--to=i.matveychikov@securitycode.ru \
--cc=davem@davemloft.net \
--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).