Re: [ovs-dev] [PATCH v4] acinclude: Autodetect DPDK location when configuring OVS
On 08/04/16 10:17, Panu Matilainen wrote: > In the autodetection mode both -I/usr/local/include/dpdk and > -I/usr/include/dpdk are specified during compilation which seems a bit > questionable but how harmful it actually is I dunno, the chances that > you have two different versions in /usr/local and /usr seem fairly slim :) > > - Panu - Hi, Yeah that works for me as well. Thanks for taking care of that. -- markos ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] [PATCH] Add configurable OpenFlow port name.
On Friday, April 8, 2016, Xiao Liang wrote: > > Add new column "ofname" in Interface table to configure port name reported > to controllers with OpenFlow protocol, thus decouple OpenFlow port name from > device name. > > For example: > # ovs-vsctl set Interface eth0 ofname=wan > # ovs-vsctl set Interface eth1 ofname=lan0 > then controllers can recognize ports by their names. > Hi Xiao, Could external-ids be used to serve the same purpose? E.g. ovs-vsctl set Interface eth0 external-ids:ofname=wan. Han ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
[ovs-dev] Delivery reports about your e-mail
The original message was received at Sun, 10 Apr 2016 08:45:12 +0800 from 163.67.173.33 - The following addresses had permanent fatal errors - dev@openvswitch.org - Transcript of the session follows - ... while talking to 61.39.165.36: 554 5.0.0 Service unavailable; [104.4.251.152] blocked using bl.spamcop.net Session aborted ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] [PATCH] Add configurable OpenFlow port name.
On Sun, Apr 10, 2016 at 7:08 AM, Han Zhou wrote: > > On Friday, April 8, 2016, Xiao Liang wrote: >> >> Add new column "ofname" in Interface table to configure port name reported >> to controllers with OpenFlow protocol, thus decouple OpenFlow port name >> from >> device name. >> >> For example: >> # ovs-vsctl set Interface eth0 ofname=wan >> # ovs-vsctl set Interface eth1 ofname=lan0 >> then controllers can recognize ports by their names. >> > > Hi Xiao, > > Could external-ids be used to serve the same purpose? E.g. ovs-vsctl set > Interface eth0 external-ids:ofname=wan. Hi Han, As is in the schema doc, external_ids is used by external frameworks rather than OVS, assume you probably mean other_config? Do you prefer this approach because it needn't change the schema? I added a new column because openflow name is a basic property of ports, and seems good to align with "ofport" and "ofport_request". Also it would be easier to show with "ovs-vsctl show". What's your opinion? Thanks, Xiao ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
[ovs-dev] From Miss. Taala AlLiby
Hello Dear, Greetings from me. It is wonderful to contact you, i saw your profile today and became interested In you, i will also like to know you the more, I wish you will have the desire so that we can get acquainted to each other. Life itself is a mystery, no one knows tomorrow till it comes. (Remember that distance or colour does not matter but love and honest matters a lot in life) My name is Taala M. Al-Liby. I will be happy if you reply me. My Regards, Miss. Taala AlLiby --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. http://www.avast.com ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
