Re: [ovs-dev] [PATCH v7] netdev-dpdk: Enable Rx checksum offloading feature on DPDK physical ports.

On Thu, Dec 15, 2016 at 4:07 AM, Chandran, Sugesh wrote: > > > Regards > _Sugesh > >> -Original Message- >> From: Pravin Shelar [mailto:pshe...@ovn.org] >> Sent: Wednesday, December 14, 2016 9:42 PM >> To: Chandran, Sugesh >> Cc: ovs dev ; Jesse Gross ; Ben >> Pfaff >> Subject: Re: [ovs-

Re: [ovs-dev] [PATCH 0/8] port Jiri's 8 support patches for layer 3 encapsulated packets from net-next

On Thu, Dec 15, 2016 at 5:23 PM, Joe Stringer wrote: > On 15 December 2016 at 05:27, Yi Yang wrote: >> This patch set just ports Jiri's 8 support patches for layer 3 encapsulated >> packets from net-next to current ovs, this is a cornerstone for L3 tunnel >> port support in ovs. > > Please foll

Re: [ovs-dev] Backporting "net: mpls: Fixups for GSO"

On Thu, Dec 15, 2016 at 4:33 PM, Jarno Rajahalme wrote: > Simon, > > I was looking at backporting upstream commit 48d2ab609b6b (“net: mpls: Fixups > for GSO”), but quickly figured out I’m out of my depth here. > > This commit changes how the skb offsets are set up for an MPLS packet, but > seems

[ovs-dev] [PATCH v1 1/2] sflow: restrict sampling from 1 to UINT32_MAX

When sampling field is 0, no need to generate sample or the inner action. --- ofproto/ofproto-dpif-xlate.c | 5 + vswitchd/vswitch.ovsschema | 7 +-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/ofproto/ofproto-dpif-xlate.c b/ofproto/ofproto-dpif-xlate.c index d0f9a33.

[ovs-dev] [PATCH v1 2/2] ofproto-dpif-xlate: optimize 100% sampling

For 100% sampling, no need to use sample action. Just use userspace action for optimizing. --- ofproto/ofproto-dpif-xlate.c | 26 +- tests/ofproto-dpif.at| 10 +- 2 files changed, 22 insertions(+), 14 deletions(-) diff --git a/ofproto/ofproto-dpif-xlate.c b

Re: [ovs-dev] [PATCH 3/3 v6] Windows: document multiple NIC support setup

Thanks a lot for the review! I posted a new version under: http://patchwork.ozlabs.org/patch/706217/ I hope I tackled all the issues. Thanks, Alin. > -Original Message- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > boun...@openvswitch.org] On Behalf Of Stephen Finucane > Sen

[ovs-dev] [PATCH] windows: WSAPoll broken on windows

Unfortunately, WSAPoll misbehaves on Windows please view detailed behavior on: https://github.com/openvswitch/ovs-issues/issues/117 We replace the WSAPoll with select looking only for errors and write events. Signed-off-by: Alin Gabriel Serdean Reported-at: https://github.com/openvswitch/ovs-iss

[ovs-dev] [PATCH] lib/ovs-thread: set prefer writer lock for ovs_rwlock_init()

From: zangchuanqiang An alternative "writer nonrecursive" rwlock allows recursive read-locks to succeed only if there are no threads waiting for the write-lock. In the function ovs_rwlock_init(), there exist a problem, the parameter of 'attr' is not used to set the attributes of ovs_rwlock 'l_',

[ovs-dev] You have received a Secure Message

Dear Customer, You have received an encrypted message from serv...@dfat.gov.au. The sender intended for the message contents to be secured. You can retrieve the message from the Message Center. If you would like to save a copy of the email or attachment, please save from the opened encryp

Re: [ovs-dev] [PATCH 0/8] port Jiri's 8 support patches for layer 3 encapsulated packets from net-next

On 15 December 2016 at 05:27, Yi Yang wrote: > This patch set just ports Jiri's 8 support patches for layer 3 encapsulated > packets from net-next to current ovs, this is a cornerstone for L3 tunnel > port support in ovs. Please follow the directions for submitting patches: http://docs.openvswi

[ovs-dev] GOOD DAY

i greet you hope am not offending you,you got me interested on adultpage how you doing? love to have a world with you okay ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] Backporting "net: mpls: Fixups for GSO"

Simon, I was looking at backporting upstream commit 48d2ab609b6b (“net: mpls: Fixups for GSO”), but quickly figured out I’m out of my depth here. This commit changes how the skb offsets are set up for an MPLS packet, but seems to omit the corresponding changes to key_extract() so that MPLS pack

Re: [ovs-dev] FINANCING YOUR PROJECT

- This mail is in HTML. Some elements may be ommited in plain text. - Fund available for investment please get in touch for more details. Regional Representative Sheikh Naseefa Investment Group Company ___ dev mailing list d...@openvswitch.org https://m

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

Hi, Thank you for the constructive meeting. Here are my notes: Date: 2016-12-15, 8-9:30 am CET Participants: Yi Yang, Danny Zhou, Zoltan Balogh, Jan Scheurich Summary: * Went through the proposed solution for NSH based on PTAP and generic encap/decap in the doc: https://docs.google.com

Re: [ovs-dev] [PATCH 9/9] ovn-controller: Drop most uses of OVS patch ports.

On Thu, Dec 15, 2016 at 11:17:57AM -0800, Mickey Spiegel wrote: > On Thu, Dec 15, 2016 at 10:15 AM, Ben Pfaff wrote: > > > On Wed, Dec 07, 2016 at 10:46:22AM -0800, Ben Pfaff wrote: > > > On Wed, Dec 07, 2016 at 10:08:25AM -0800, Guru Shetty wrote: > > > > On 4 December 2016 at 23:17, Ben Pfaff

Re: [ovs-dev] strong empheral references?

On Thu, Dec 15, 2016 at 03:59:34PM -0600, Marcelo E. Magallon wrote: > The RFC contains this: > > If "ephemeral" is specified as true, then this column's values > are not guaranteed to be durable; they may be lost when the > database restarts. A column whose type (either key or

[ovs-dev] strong empheral references?

Hi! The RFC contains this: If "ephemeral" is specified as true, then this column's values are not guaranteed to be durable; they may be lost when the database restarts. A column whose type (either key or value) is a strong reference to a table that is not part of

Re: [ovs-dev] general question about synchronization in ovs

> On Dec 15, 2016, at 1:07 PM, Yuxin Ren wrote: > > On Thu, Dec 15, 2016 at 4:00 PM, Jarno Rajahalme > wrote: >> >>> On Dec 15, 2016, at 7:55 AM, Yuxin Ren wrote: >>> >>> Hi, >>> >>> I am a beginner to OVS. >>> I have some basic questions about OVS. >>> >>> Is it a mu

[ovs-dev] [RFC: fedora ovn packaging 5/5] rpms: Adding three additional OVN packages

Add ovn-northbound-database, ovn-southbound-database and ovn-northd as packages that can be installed independently. Signed-off-by: Andy Zhou --- rhel/automake.mk | 5 +- rhel/openvswitch-fedora.spec.in| 53 -- rhel/usr_l

[ovs-dev] [RFC: fedora ovn packaging 4/5] ovn-ctl: Factor out start/stop ovnsb/ovnnb

Current ovn-ctl starts and stops both southbound and northbound DBs at the same time. Future patches will provide services that start them individually. Signed-off-by: Andy Zhou --- ovn/utilities/ovn-ctl | 55 +++-- ovn/utilities/ovn-ctl.8.xml | 4 +

[ovs-dev] [RFC: fedora ovn packaging 3/5] rhel: Rename nrothd to central service

Future patch will make ovn-northd.server start and stop northd only. Rename the current service as central service to be more consistent with the package name. Signed-off-by: Andy Zhou --- rhel/automake.mk| 2 +- rhel/openvswitch-fedora.spec.in |

[ovs-dev] [RFC: fedora ovn packaging 2/5] rpms: Style fixes

Replace a few tabs with spaces in the file to be more consistent with the rest of the file. Signed-off-by: Andy Zhou --- rhel/openvswitch-fedora.spec.in | 23 --- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/rhel/openvswitch-fedora.spec.in b/rhel/openvswitc

[ovs-dev] [RFC: fedora ovn packaging 0/5] RFC fedora ovn packaging

The goal of this series is to make it easier to set up OVN in a larger setup, i.e. not having all services running on a single host. Currently ovn-central package starts and stop all three services northbound-db, northd and southbound-db on the same host. While it is convenient for a single host s

[ovs-dev] [RFC: fedora ovn packaging 1/5] rpms: Seperate ovsdb-server into its own package

In case a system is dedicated to run OVN southbound (or northbound) database, It only needs to run ovsdb-server. It would be nice not have to install or run ovs-vswitchd. Signed-off-by: Andy Zhou --- rhel/openvswitch-fedora.spec.in | 55 - 1 file changed,

Re: [ovs-dev] [PATCH 1/3 v7] Windows: Add internal switch port per OVS bridge

I hope the following answers your questions. Alin. From: Shashank Ram [mailto:r...@vmware.com] Sent: Thursday, December 15, 2016 10:27 PM To: Alin Serdean ; d...@openvswitch.org Subject: Re: [ovs-dev] [PATCH 1/3 v7] Windows: Add internal switch port per OVS bridge Thanks Alin. I had a few other

Re: [ovs-dev] general question about synchronization in ovs

On Thu, Dec 15, 2016 at 4:00 PM, Jarno Rajahalme wrote: > >> On Dec 15, 2016, at 7:55 AM, Yuxin Ren wrote: >> >> Hi, >> >> I am a beginner to OVS. >> I have some basic questions about OVS. >> >> Is it a multiple threads application? > > Yes. > >> If so, what data structures are shared by multiple

Re: [ovs-dev] general question about synchronization in ovs

> On Dec 15, 2016, at 7:55 AM, Yuxin Ren wrote: > > Hi, > > I am a beginner to OVS. > I have some basic questions about OVS. > > Is it a multiple threads application? Yes. > If so, what data structures are shared by multiple threads? Most of them, e.g., flow tables, group tables, and most o

Re: [ovs-dev] [PATCH 1/3 v7] Windows: Add internal switch port per OVS bridge

Thanks Alin. I had a few other questions. 1. For new ports being added to a bridge, will the ports be created only if its type=internal? 2. Is there a reason to disable the adapter to rename it? If the adapter was previously enabled, why is it left to the user to enable it? __

Re: [ovs-dev] [PATCH 1/3 v7] Windows: Add internal switch port per OVS bridge

Hi Shashank, Ovs-vsctl add-br does not change the current behaviour. Ovs-vsctl add-br creates an internal port automatically (think of specifying type=internal automatically). Same applies for ovs-vsctl del-br Please view the output of the command: ovsdb-client dump -f html in the attachment (

Re: [ovs-dev] [PATCH 1/3 v7] Windows: Add internal switch port per OVS bridge

Hi Alin, please find my comments inline. Thanks, Shashank From: ovs-dev-boun...@openvswitch.org on behalf of Alin Serdean Sent: Thursday, December 15, 2016 11:36 AM To: d...@openvswitch.org Subject: [ovs-dev] [PATCH 1/3 v7] Windows: Add internal switch port per

[ovs-dev] [PATCH 2/3 v7] datapath-windows: Add multiple switch internal ports

This patch adds multiple internal ports support to the windows datapath. All tunnels types have been updated to accommodate this new functionality. Signed-off-by: Alin Gabriel Serdean Co-authored-by: Sorin Vinturis Acked-by: Paul Boca --- v7: Rebase v6: Rebase v5: Rebase v4: Address comments (

[ovs-dev] [PATCH 3/3 v7] Windows: document multiple NIC support setup

This patch updates the documentation on how to set up OVS with multiple NICs. Also update the documentation to show users how new internal ports are created Signed-off-by: Alin Gabriel Serdean Acked-by: Paul Boca --- v7: Address Stephen's comments v6: rebase v5: rebase v4: rebase v3: rebase v2:

[ovs-dev] [PATCH 1/3 v7] Windows: Add internal switch port per OVS bridge

This patch updates the following commands in the vswitch: ovs-vsctl add-br br-test ovs-vsctl del-br br-test ovs-vsctl add-br br-test: This command will now create an internal port on the MSFT virtual switch using the WMI interface from Msvm_VirtualEthernetSwitchManagementService leveragi

[ovs-dev] [PATCH 1/3 v7] Windows: Add internal switch port per OVS bridge

This patch updates the following commands in the vswitch: ovs-vsctl add-br br-test ovs-vsctl del-br br-test ovs-vsctl add-br br-test: This command will now create an internal port on the MSFT virtual switch using the WMI interface from Msvm_VirtualEthernetSwitchManagementService leveragi

Re: [ovs-dev] [PATCH 9/9] ovn-controller: Drop most uses of OVS patch ports.

On Thu, Dec 15, 2016 at 10:15 AM, Ben Pfaff wrote: > On Wed, Dec 07, 2016 at 10:46:22AM -0800, Ben Pfaff wrote: > > On Wed, Dec 07, 2016 at 10:08:25AM -0800, Guru Shetty wrote: > > > On 4 December 2016 at 23:17, Ben Pfaff wrote: > > > > > > > Until now, ovn-controller has implemented OVN logical

[ovs-dev] [PATCH] [RFC] ovn: Support ARP proxy in logical switches.

This patch support "arp_proxy" option for logical switch ports. If a lsp with arp_proxy=true, all the arp request to known ipv4 addresses on the ls will be responded with the arp proxy lsp's MAC address, except when the arp request come from the arp proxy lsp itself. TODO: update ovn-northd.xml, a

[ovs-dev] Cloud Stack leads

Hello, We want to know whether you are interested, in Cloud Stack leads for your marketing effort. Information Available: -First Name, Last Name, Contact Name, Title, Company, Address, City, State/Province, ZIP/Postal Code, ZIP4, Country, Phone, Fax, Primary Industry, SIC Code, NAICS, Employees,

Re: [ovs-dev] [PATCH 9/9] ovn-controller: Drop most uses of OVS patch ports.

On Wed, Dec 07, 2016 at 10:46:22AM -0800, Ben Pfaff wrote: > On Wed, Dec 07, 2016 at 10:08:25AM -0800, Guru Shetty wrote: > > On 4 December 2016 at 23:17, Ben Pfaff wrote: > > > > > Until now, ovn-controller has implemented OVN logical patch ports and > > > l3gateway ports in terms of OVS patch p

Re: [ovs-dev] [PATCH 9/9] ovn-controller: Drop most uses of OVS patch ports.

On Mon, Dec 05, 2016 at 12:58:24PM -0800, Mickey Spiegel wrote: > On Sun, Dec 4, 2016 at 11:17 PM, Ben Pfaff wrote: > > > Until now, ovn-controller has implemented OVN logical patch ports and > > l3gateway ports in terms of OVS patch ports. It is a hassle to create and > > destroy ports, and it

[ovs-dev] Auditorías a través del Buzón Tributario

En línea y en Vivo / Para todo su Equipo con una sola Conexión Auditorías a través del Buzón Tributario 29 de diciembre - Online en Vivo - 10:00 a 13:00 Hrs A través de esta Capacitación Online en Vivo entérese cuáles son los sectores involucrados, en qué consisten dichas auditorías,

Re: [ovs-dev] [RFC PATCHv2] ofp-actions: Add clone action.

On Thu, Dec 15, 2016 at 07:38:15AM -0800, William Tu wrote: > > Here are some examples of translations from OpenFlow to datapath > > actions, the way I would expect them to happen: > > > > OF: 1, clone(truncate(100), push_vlan, 2), 3 > > dp: 1, truncate(100), push_vlan, 2, pop_vlan, 3 > > >

[ovs-dev] general question about synchronization in ovs

Hi, I am a beginner to OVS. I have some basic questions about OVS. Is it a multiple threads application? If so, what data structures are shared by multiple threads? What synchronization technique is used to protect shared data structures? Thanks a lot!! Yuxin

Re: [ovs-dev] [RFC PATCHv2] ofp-actions: Add clone action.

> Here are some examples of translations from OpenFlow to datapath > actions, the way I would expect them to happen: > > OF: 1, clone(truncate(100), push_vlan, 2), 3 > dp: 1, truncate(100), push_vlan, 2, pop_vlan, 3 > I see your point; the "clone" is handled at translation code, and pop_vla

[ovs-dev] [RFC v3 3/5] ovn: move load balancing flows after NAT flows

This will make it easy for distributed NAT to reuse some of the existing code for NAT flows, while leaving load balancing and defrag as functionality specific to gateway routers. There is no intent to change any functionality in this patch. Signed-off-by: Mickey Spiegel --- ovn/northd/ovn-north

[ovs-dev] [RFC v3 0/5] ovn: add distributed NAT capability

Currently OVN supports NAT functionality by connecting each distributed logical router to a centralized "l3gateway" router that resides on a single chassis. NAT is only carried out in the "l3gateway" router. This patch set introduces NAT capability in the distributed logical router itself, avoidi

[ovs-dev] [RFC v3 5/5] ovn: distributed NAT flows

This patch implements the flows required in the ingress and egress pipeline stages in order to support NAT on a distributed logical router. NAT functionality is associated with the logical router gateway port. The flows that carry out NAT functionality all have match conditions on inport or outpor

[ovs-dev] [RFC v3 4/5] ovn: avoid snat recirc only on gateway routers

Currently, for performance reasons on gateway routers, ct_snat that does not specify an IP address does not immediately trigger recirculation. On gateway routers, ct_snat that does not specify an IP address happens in the UNSNAT pipeline stage, which is followed by the DNAT pipeline stage that tri

[ovs-dev] [RFC v3 2/5] ovn: Introduce "chassisredirect" port binding

Currently OVN handles all logical router ports in a distributed manner, creating instances on each chassis. The logical router ingress and egress pipelines are traversed locally on the source chassis. In order to support advanced features such as one-to-many NAT (aka IP masquerading), where multi

[ovs-dev] [RFC v3 1/5] ovn: add is_chassis_resident match expression component

This patch introduces a new match expression component is_chassis_resident(). Unlike match expression comparisons, is_chassis_resident is not pushed down to OpenFlow. It is a conditional that is evaluated in the controller during expr_simplify(), when it is replaced by a boolean expression. The

[ovs-dev] [PATCH 8/8] datapath: allow L3 netdev ports

>From net-next commit 217ac77a3c2524d999730b2a80b61fcc2d0f734a. Allow ARPHRD_NONE interfaces to be added to ovs bridge. Based on previous versions by Lorand Jakab and Simon Horman. Signed-off-by: Lorand Jakab Signed-off-by: Simon Horman Signed-off-by: Jiri Benc Acked-by: Pravin B Shelar Sign

[ovs-dev] [PATCH 7/8] datapath: add Ethernet push and pop actions

>From net-next 91820da6ae85904d95ed53bf3a83f9ec44a6b80a. It's not allowed to push Ethernet header in front of another Ethernet header. It's not allowed to pop Ethernet header if there's a vlan tag. This preserves the invariant that L3 packet never has a vlan tag. Based on previous versions by Lo

[ovs-dev] [PATCH 6/8] datapath: netlink: support L3 packets

>From net-next commit 0a6410fbde597ebcf82dda4a0b0e889e82242678. Extend the ovs flow netlink protocol to support L3 packets. Packets without OVS_KEY_ATTR_ETHERNET attribute specify L3 packets; for those, the OVS_KEY_ATTR_ETHERTYPE attribute is mandatory. Push/pop vlan actions are only supported fo

[ovs-dev] [PATCH 5/8] datapath: add processing of L3 packets

>From net-next commit 5108bbaddc37c1c8583f0cf2562d7d3463cd12cb. Support receiving, extracting flow key and sending of L3 packets (packets without an Ethernet header). Note that even after this patch, non-Ethernet interfaces are still not allowed to be added to bridges. Similarly, netlink interfac

[ovs-dev] [PATCH 4/8] datapath: support MPLS push and pop for L3 packets

>From net-next commit 1560a074df6297e76278e459ca3eb9ff83a6f878. Update Ethernet header only if there is one. Signed-off-by: Jiri Benc Acked-by: Pravin B Shelar Signed-off-by: David S. Miller Signed-off-by: Yi Yang --- datapath/actions.c | 18 +++--- 1 file changed, 11 insertions(

[ovs-dev] [PATCH 3/8] datapath: pass mac_proto to ovs_vport_send

>From net-next commit e2d9d8358cb961340ef88620b6a25ba4557033d5 We'll need it to alter packets sent to ARPHRD_NONE interfaces. Change do_output() to use the actual L2 header size of the packet when deciding on the minimum cutlen. The assumption here is that what matters is not the output interface

[ovs-dev] [PATCH 2/8] datapath: add mac_proto field to the flow key

>From net-next commit 329f45bc4f191c663dc156c510816411a4310578. Use a hole in the structure. We support only Ethernet so far and will add a support for L2-less packets shortly. We could use a bool to indicate whether the Ethernet header is present or not but the approach with the mac_proto field i

[ovs-dev] [PATCH 1/8] datapath: use hard_header_len instead of hardcoded ETH_HLEN

>From net-next commit 738314a084aae5f76ff760279034b39d52c42e8b. On tx, use hard_header_len while deciding whether to refragment or drop the packet. That way, all combinations are calculated correctly: * L2 packet going to L2 interface (the L2 header len is subtracted), * L2 packet going to L3 int

[ovs-dev] [PATCH 0/8] port Jiri's 8 support patches for layer 3 encapsulated packets from net-next

This patch set just ports Jiri's 8 support patches for layer 3 encapsulated packets from net-next to current ovs, this is a cornerstone for L3 tunnel port support in ovs. Yi Yang (8): datapath: use hard_header_len instead of hardcoded ETH_HLEN datapath: add mac_proto field to the flow key

Re: [ovs-dev] [PATCH v2 4/4] datapath-windows: Conntrack - Enable FTP support

Acked-by: Alin Gabriel Serdean > -Original Message- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > boun...@openvswitch.org] On Behalf Of Sairam Venugopal > Sent: Friday, December 9, 2016 10:05 PM > To: d...@openvswitch.org > Subject: [ovs-dev] [PATCH v2 4/4] datapath-windows:

Re: [ovs-dev] [PATCH v2 3/4] datapath-windows: Conntrack - Introduce support for tracking related connections

../ovs-dev-v2-3-4-datapath-windows-Conntrack---Introduce-support-for-tracking-related-connections.patch:564: new blank line at EOF. + warning: 1 line adds whitespace errors. Acked-by: Alin Gabriel Serdean > -Original Message- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > b

Re: [ovs-dev] [PATCH v2 2/4] datapath-windows: Cleanup Conntrack definitions and introduce related entries

Acked-by: Alin Gabriel Serdean > -Original Message- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > boun...@openvswitch.org] On Behalf Of Sairam Venugopal > Sent: Friday, December 9, 2016 10:05 PM > To: d...@openvswitch.org > Subject: [ovs-dev] [PATCH v2 2/4] datapath-windows:

Re: [ovs-dev] [PATCH v2 1/4] datapath-windows: Conntrack - Fix OvsGetTcpPayloadLength()

Just a small alignment problem. Acked-by: Alin Gabriel Serdean > -Original Message- > From: ovs-dev-boun...@openvswitch.org [mailto:ovs-dev- > boun...@openvswitch.org] On Behalf Of Sairam Venugopal > Sent: Friday, December 9, 2016 10:05 PM > To: d...@openvswitch.org > Subject: [ovs-dev]

Re: [ovs-dev] [PATCH v7] netdev-dpdk: Enable Rx checksum offloading feature on DPDK physical ports.

Regards _Sugesh > -Original Message- > From: Pravin Shelar [mailto:pshe...@ovn.org] > Sent: Wednesday, December 14, 2016 9:42 PM > To: Chandran, Sugesh > Cc: ovs dev ; Jesse Gross ; Ben > Pfaff > Subject: Re: [ovs-dev] [PATCH v7] netdev-dpdk: Enable Rx checksum > offloading feature on

Re: [ovs-dev] [PATCH v2 2/3] netdev-dpdk: Arbitrary 'dpdk' port naming

> > Thanks for the new version, I'm still testing this. Thanks Daniele. I plan to do some more thorough testing myself. > > One comment inline > > 2016-12-14 9:06 GMT-08:00 Ciara Loftus : > > 'dpdk' ports no longer have naming restrictions. Now, instead of > > specifying the dpdk port ID as pa

[ovs-dev] [PATCH v3 3/3] netdev-dpdk: Add support for virtual DPDK PMDs (vdevs)

Prior to this commit, the 'dpdk' port type could only be used for physical DPDK devices. Now, virtual devices (or 'vdevs') are supported. 'vdev' devices are those which use virtual DPDK Poll Mode Drivers eg. null, pcap. To add a DPDK vdev, a valid 'dpdk-devargs' must be set for the given dpdk port.

[ovs-dev] [PATCH v3 1/3] netdev-dpdk: add hotplug support

In order to use dpdk ports in ovs they have to be bound to a DPDK compatible driver before ovs is started. This patch adds the possibility to hotplug (or hot-unplug) a device after ovs has been started. The implementation adds two appctl commands: netdev-dpdk/attach and netdev-dpdk/detach After t

[ovs-dev] [PATCH v3 2/3] netdev-dpdk: Arbitrary 'dpdk' port naming

'dpdk' ports no longer have naming restrictions. Now, instead of specifying the dpdk port ID as part of the name, the PCI address of the device must be specified via the 'dpdk-devargs' option. eg. ovs-vsctl add-port br0 my-port ovs-vsctl set Interface my-port type=dpdk ovs-vsctl set Interface my-p

[ovs-dev] [PATCH v1] sflow: restrict sampling from 1 to UINT32_MAX

When sampling field is 0, no need to generate sample or the inner action. --- ofproto/ofproto-dpif-xlate.c | 5 + vswitchd/vswitch.ovsschema | 7 +-- 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/ofproto/ofproto-dpif-xlate.c b/ofproto/ofproto-dpif-xlate.c index d0f9a33.