netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Emelianov <xemul@openvz.org>
To: Patrick McHardy <kaber@trash.net>
Cc: David Miller <davem@davemloft.net>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Daniel Lezcano <dlezcano@fr.ibm.com>,
	Ben Greear <greearb@candelatech.com>,
	devel@openvz.org, Kirill Korotaev <dev@openvz.org>
Subject: Re: [PATCH] Virtual ethernet device (v2.1)
Date: Wed, 11 Jul 2007 16:44:53 +0400	[thread overview]
Message-ID: <4694D0C5.6020700@openvz.org> (raw)
In-Reply-To: <4694CBD9.90503@trash.net>

Patrick McHardy wrote:
> Pavel Emelianov wrote:
>> +static const struct nla_policy veth_policy[VETH_INFO_MAX + 1] = {
>> +	[VETH_INFO_MAC]		= { .type = NLA_BINARY, .len = ETH_ALEN },
>> +	[VETH_INFO_PEER]	= { .type = NLA_STRING },
>> +	[VETH_INFO_PEER_MAC]	= { .type = NLA_BINARY, .len = ETH_ALEN },
>> +};
> 
> 
> Looks good, just one question. What happended to the IFLA_PARTNER
> attribute idea? I have a patch to allow specifying the initial
> MAC address for a device, IFLA_PARTNER would make the whole thing
> symetrical.

Well, the notion of a partner is not applicable to any generic link
unlike the device name, physical (MAC) address or MTU value. So i 
think that it's better to keep this as a specific driver information 
not to confuse the generic code. I think it's worth making this as 
some more generic code than it is now, but since this driver is the 
only user of "partner" maybe it's better not to make it right now. 
Later, when we do know what do we want "partner" to be.

Thanks,
Pavel

  reply	other threads:[~2007-07-11 12:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11  9:31 [PATCH] Virtual ethernet device (v2.1) Pavel Emelianov
2007-07-11  9:33 ` [PATCH] Module for ip utility to support veth device (v.2.1) Pavel Emelianov
2007-07-11  9:44 ` [PATCH] Virtual ethernet device (v2.1) Evgeniy Polyakov
2007-07-11 10:54 ` Christian Borntraeger
2007-07-11 12:24   ` Pavel Emelianov
2007-07-11 20:45   ` David Miller
2007-07-11 12:23 ` Patrick McHardy
2007-07-11 12:44   ` Pavel Emelianov [this message]
2007-07-11 12:53     ` Patrick McHardy
2007-07-11 13:00       ` Pavel Emelianov
2007-07-11 13:12         ` Patrick McHardy
2007-07-11 13:32           ` Pavel Emelianov
2007-07-11 17:32             ` Patrick McHardy

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=4694D0C5.6020700@openvz.org \
    --to=xemul@openvz.org \
    --cc=davem@davemloft.net \
    --cc=dev@openvz.org \
    --cc=devel@openvz.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=greearb@candelatech.com \
    --cc=kaber@trash.net \
    --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).