netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Jiri Benc <jbenc@redhat.com>
Cc: Vincent Bernat <vincent@bernat.im>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: [PATCH] veth: replace iflink by a dedicated symlink in sysfs
Date: Thu, 20 Aug 2015 16:31:11 +0200	[thread overview]
Message-ID: <55D5E4AF.7020409@6wind.com> (raw)
In-Reply-To: <20150820135307.3ce12f69@griffin>

Le 20/08/2015 13:53, Jiri Benc a écrit :
> On Wed, 19 Aug 2015 18:33:14 +0200, Nicolas Dichtel wrote:
>> Probably better to introduce veth netlink attribute then, something like
>> IFLA_VETH_PEER and keeps IFLA_LINK_NETNSID.
>
> I'd prefer IFLA_PEER. More generic attribute will be helpful should we
> introduce an interface similar to veth in the future.s
Ok.

>
> Also, I'd not combine IFLA_LINK_NETNSID with IFLA_PEER. There might
> very well be an interface in the future that will need both IFLA_LINK and
> IFLA_PEER and this would just create a confusion. It may be unlikely
> but the attributes are cheap and it doesn't make sense to design uAPI
> in a way that might bring problems in the future.
Ok, but then this IFLA_PEER can include the ifindex and the nsid. No need
to have two new attributes.

>
>> I also don't know what is the best way to handle this. veth advertises
>> its peer via IFLA_LINK since 4.1, so it's too late to change it for this
>> release.
>
> Apparently we need to pick our poison. Either way, we break something.
Sure. I would prefer to have the same mechanism in all version, but I can
live with the other solution.

David, any thoughts about this?

  reply	other threads:[~2015-08-20 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87fv3ier4s.fsf@zoro.exoscale.ch>
2015-08-19  6:44 ` Regression in 4.1 with veth and IFLA_LINK Vincent Bernat
2015-08-19  6:44   ` [PATCH] veth: replace iflink by a dedicated symlink in sysfs Vincent Bernat
2015-08-19 11:00     ` Jiri Benc
2015-08-19 12:13       ` Vincent Bernat
2015-08-19 12:38         ` Jiri Benc
2015-08-19 12:48           ` Vincent Bernat
2015-08-19 16:33             ` Nicolas Dichtel
2015-08-20 11:53               ` Jiri Benc
2015-08-20 14:31                 ` Nicolas Dichtel [this message]
2015-08-20 21:07                   ` David Miller
2015-08-22 20:51                     ` Vincent Bernat

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=55D5E4AF.7020409@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=davem@davemloft.net \
    --cc=jbenc@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=vincent@bernat.im \
    /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).