From: Arnd Bergmann <arnd@arndb•de>
To: Scott Feldman <scofeldm@cisco•com>
Cc: netdev@vger•kernel.org, Chris Wright <chrisw@redhat•com>,
Stephen Hemminger <shemminger@vyatta•com>,
Stefan Berger <stefanb@us•ibm.com>,
Dirk Herrendoerfer <d.herrendoerfer@de•ibm.com>,
Vivek Kashyap <vivk@us•ibm.com>
Subject: Re: [RFC] IFLA_PORT_* iproute2 cmd line
Date: Thu, 27 May 2010 09:00:29 +0200 [thread overview]
Message-ID: <201005270900.29776.arnd@arndb.de> (raw)
In-Reply-To: <C8228316.35508%scofeldm@cisco.com>
On Wednesday 26 May 2010, Scott Feldman wrote:
> On 5/26/10 5:38 AM, "Arnd Bergmann" <arnd@arndb•de> wrote:
>
> How does this strike you?
>
> Usage: ip link add link DEV [ name ] NAME
> [ txqueuelen PACKETS ]
> [ address LLADDR ]
> [ broadcast LLADDR ]
> [ mtu MTU ]
> type TYPE [ ARGS ]
> ip link delete DEV type TYPE [ ARGS ]
>
> ip link set DEVICE [ { up | down } ]
> [ arp { on | off } ]
> [ dynamic { on | off } ]
> [ multicast { on | off } ]
> [ allmulticast { on | off } ]
> [ promisc { on | off } ]
> [ trailers { on | off } ]
> [ txqueuelen PACKETS ]
> [ name NEWNAME ]
> [ address LLADDR ]
> [ broadcast LLADDR ]
> [ mtu MTU ]
> [ netns PID ]
> [ alias NAME ]
> + [ virtualport MODE {PROFILE|VSI} ]
> [ vf NUM [ mac LLADDR ]
> [ vlan VLANID [ qos VLAN-QOS ] ]
> - [ rate TXRATE ] ]
> + [ rate TXRATE ]
> + [ virtualport MODE {PROFILE|VSI} ] ]
> ip link show [ DEVICE ]
>
> TYPE := { vlan | veth | vcan | dummy | ifb | macvlan | can }
> +
> + MODE := { associate | preassociate | preassociaterr | disassociate }
> +
> + PROFILE := port-profile PORT-PROFILE
> + [ instance-uuid INSTANCE-UUID ]
> + [ host-uuid HOST-UUID ]
> +
> + VSI := vsi managerid MGR typeid VTID typeidversion VER
> + [ instance-uuid INSTANCE-UUID ]
Right, exactly what I was thinking of. I would probably use
some shorter keywords (virtual-port -> port, port-profile -> profile,
instance-uuid -> instance, host-uuid -> host), but I really
don't have a strong opionion on that, so I'f fine with
whatever you and others come up with in that regard.
> > The more interesting question is how to do this when we
> > talk to lldpad. One idea was to use the same protocol
> > but to direct the message to a specific pid (that of lldpad).
> > That would require adding an option like '-p PID' to ip
> > that lets us change who we talk to.
>
> Let me get the user-to-kernel part working to establish the cmd line and you
> can follow up with alternative addressing schemes.
ok.
Arnd
next prev parent reply other threads:[~2010-05-27 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 3:19 [RFC] IFLA_PORT_* iproute2 cmd line Scott Feldman
2010-05-26 12:38 ` Arnd Bergmann
2010-05-26 14:49 ` Scott Feldman
2010-05-27 7:00 ` Arnd Bergmann [this message]
[not found] ` <OFCF88A167.122DD206-ON8525772F.00470999-8525772F.0047F4A5@us.ibm.com>
2010-05-26 15:56 ` Chris Wright
[not found] ` <OFB3363EDA.945755DA-ON8525772F.0057CBD1-8525772F.00589D2B@us.ibm.com>
2010-05-26 16:15 ` Arnd Bergmann
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=201005270900.29776.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=chrisw@redhat$(echo .)com \
--cc=d.herrendoerfer@de$(echo .)ibm.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=scofeldm@cisco$(echo .)com \
--cc=shemminger@vyatta$(echo .)com \
--cc=stefanb@us$(echo .)ibm.com \
--cc=vivk@us$(echo .)ibm.com \
/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