From: Lance Richardson <lrichard@redhat•com>
To: nicolas dichtel <nicolas.dichtel@6wind•com>
Cc: Vincent Bernat <vincent@bernat•im>,
"David S. Miller" <davem@davemloft•net>,
Vijay Pandurangan <vijayp@vijayp•ca>,
Paolo Abeni <pabeni@redhat•com>,
netdev@vger•kernel.org
Subject: Re: [net v3] veth: advertise peer link once both links are tied together
Date: Fri, 10 Jun 2016 09:20:58 -0400 (EDT) [thread overview]
Message-ID: <1764704950.51133004.1465564858359.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <575ABD55.7020202@6wind.com>
----- Original Message -----
> From: "Nicolas Dichtel" <nicolas.dichtel@6wind•com>
> To: "Lance Richardson" <lrichard@redhat•com>, "Vincent Bernat" <vincent@bernat•im>
> Cc: "David S. Miller" <davem@davemloft•net>, "Vijay Pandurangan" <vijayp@vijayp•ca>, "Paolo Abeni"
> <pabeni@redhat•com>, netdev@vger•kernel.org
> Sent: Friday, June 10, 2016 9:15:01 AM
> Subject: Re: [net v3] veth: advertise peer link once both links are tied together
>
> Le 08/06/2016 22:30, Lance Richardson a écrit :
> [snip]
> > I've been pondering how to fix this very problem off-and-on for a few
> > months
> > now, without having arrived at any solution that was particularly
> > satisfying.
> >
> > The main constraints I've been trying to meet are:
> > - User-space should be informed of veth pairing for both peers.
> > - RTM_NEWLINK messages should not refer to interfaces that haven't
> > been announced to user-space via previous RTM_NEWLINK messages.
> > - The first (and only the first) RTM_NEWLINK message for a given
> > interface should have ifi_changes set to ~0U, subsequent RTM_NEWLINK
> > messages should have ifi_changes set to reflect the flags that
> > have changed.
> >
> > This is the closest I've come to a satisfactory solution, it does meet
> > the above constraints but still seems a little unnatural to me:
> The patch looks good to me. Can you submit it formally?
>
Will post in a bit, thanks!
Lance
next prev parent reply other threads:[~2016-06-10 13:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 11:17 [PATCH] veth: delay peer link configuration after interfaces are tied Vincent Bernat
2016-05-30 9:23 ` Nicolas Dichtel
2016-05-30 10:11 ` Vincent Bernat
2016-05-30 15:19 ` Nicolas Dichtel
2016-05-30 15:26 ` Vincent Bernat
2016-05-30 15:47 ` Nicolas Dichtel
2016-05-30 15:58 ` [net v3] veth: advertise peer link once both links are tied together Vincent Bernat
2016-05-30 16:01 ` Vincent Bernat
2016-05-30 16:27 ` Nicolas Dichtel
2016-05-31 6:29 ` Vincent Bernat
2016-05-31 9:17 ` Nicolas Dichtel
2016-06-08 20:30 ` Lance Richardson
2016-06-10 13:15 ` Nicolas Dichtel
2016-06-10 13:20 ` Lance Richardson [this message]
2016-05-31 6:30 ` [net v4] " Vincent Bernat
2016-05-31 6:54 ` Vincent Bernat
2016-05-30 10:12 ` [PATCH] veth: delay peer link configuration after interfaces are tied Vincent Bernat
2016-05-30 10:14 ` Vincent Bernat
2016-05-30 10:13 ` Vincent Bernat
2016-05-30 15:19 ` Nicolas Dichtel
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=1764704950.51133004.1465564858359.JavaMail.zimbra@redhat.com \
--to=lrichard@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nicolas.dichtel@6wind$(echo .)com \
--cc=pabeni@redhat$(echo .)com \
--cc=vijayp@vijayp$(echo .)ca \
--cc=vincent@bernat$(echo .)im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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