[ovs-discuss] failed to put[create] (Invalid argument)

2018-01-29 Thread John Lester
Hello, I'm having issues forwarding a flow that is encapsulated with nsh+ethernet. Below is the syslog error message. I'm using ovs v2.9.90 and Linux kernel 4.13.0-32-generic. Jan 29 20:23:49 checkout ovs-vswitchd: ovs|00672|dpif(handler5)|WARN|system@ovs-system: failed to put[create] (Invalid

[ovs-discuss] Open vSwitch selected as ACM SOSR Software Systems Award Winner for 2018

2018-01-29 Thread Ben Pfaff
Yesterday, the ACM SOSR awards committee announced that it was granting Open vSwitch its second annual Software Systems Award, which is given to recognize the development of a software system that has had a significant impact on SDN research, implementations, and tools. The award comes along with

Re: [ovs-discuss] Mempool issue for OVS 2.9

2018-01-29 Thread Jan Scheurich
> -Original Message- > From: Ilya Maximets [mailto:i.maxim...@samsung.com] > Sent: Monday, 29 January, 2018 09:35 > To: Jan Scheurich ; Venkatesan Pradeep > ; Stokes, Ian > ; d...@openvswitch.org > Cc:

Re: [ovs-discuss] Why no-flood is not supported in later openflow versions?

2018-01-29 Thread Ben Pfaff
On Mon, Jan 29, 2018 at 11:52:34AM +0800, Jianfeng Tan wrote: > >On Sun, Jan 28, 2018 at 11:39:29PM +0800, Jianfeng Tan wrote: > >> Hi, > >> > >> In the openflow, we set no-flood PodMod operation through openflow 1.0; > for > >> later openflow versions, no-flood is dropped. > >> We can refer to

Re: [ovs-discuss] Mempool issue for OVS 2.9

2018-01-29 Thread Kevin Traynor
On 01/26/2018 05:21 PM, Ilya Maximets wrote: > On 26.01.2018 18:47, Kevin Traynor wrote: >> hOn 01/26/2018 03:16 PM, Ilya Maximets wrote: >>> On 26.01.2018 15:00, Stokes, Ian wrote: Hi All, Recently an issue was raised regarding the move from a single shared mempool model that

Re: [ovs-discuss] Mempool issue for OVS 2.9

2018-01-29 Thread Kevin Traynor
On 01/26/2018 05:27 PM, Stokes, Ian wrote: >> -Original Message- >> From: Kevin Traynor [mailto:ktray...@redhat.com] >> Sent: Friday, January 26, 2018 3:48 PM >> To: Ilya Maximets ; Stokes, Ian >> ; ovs-discuss@openvswitch.org >> Cc: Flavio

Re: [ovs-discuss] Mempool issue for OVS 2.9

2018-01-29 Thread Stokes, Ian
> -Original Message- > From: Kevin Traynor [mailto:ktray...@redhat.com] > Sent: Monday, January 29, 2018 8:03 AM > To: Stokes, Ian ; Ilya Maximets > ; ovs-discuss@openvswitch.org > Cc: Flavio Leitner ; Loftus, Ciara >

Re: [ovs-discuss] Mempool issue for OVS 2.9

2018-01-29 Thread Jan Scheurich
Hi, I'd like to take one step back and look at how much many mbufs we actually need. Today mbufs are consumed in the following places: a) Rx queues of *physical* dpdk ports: dev->requested_n_rxq * dev->requested_rxq_size Note 1: These mbufs are hogged up at all times. Note 2: There

Re: [ovs-discuss] Mempool issue for OVS 2.9

2018-01-29 Thread Ilya Maximets
On 28.01.2018 21:34, Venkatesan Pradeep wrote: > Some more observations > > Regards, > > Pradeep > >> -Original Message- >> From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss- >> boun...@openvswitch.org] On Behalf Of Venkatesan Pradeep >> Sent: Friday, January 26, 2018

Re: [ovs-discuss] Mempool issue for OVS 2.9

2018-01-29 Thread Ilya Maximets
On 29.01.2018 11:19, Jan Scheurich wrote: > Hi, >   > I'd like to take one step back and look at how much many mbufs we actually > need. >   > Today mbufs are consumed in the following places: > > 1. Rx queues of **physical** dpdk ports: dev->requested_n_rxq * > dev->requested_rxq_size >

Re: [ovs-discuss] Mempool issue for OVS 2.9

2018-01-29 Thread Ilya Maximets
On 29.01.2018 11:50, Jan Scheurich wrote: >> -Original Message- >> From: Ilya Maximets [mailto:i.maxim...@samsung.com] >> Sent: Monday, 29 January, 2018 09:35 >> To: Jan Scheurich ; Venkatesan Pradeep >> ; Stokes, Ian >>

Re: [ovs-discuss] Why no-flood is not supported in later openflow versions?

2018-01-29 Thread Jianfeng Tan
>On Sun, Jan 28, 2018 at 11:39:29PM +0800, Jianfeng Tan wrote: >> Hi, >> >> In the openflow, we set no-flood PodMod operation through openflow 1.0; for >> later openflow versions, no-flood is dropped. >> We can refer to below two macro definitions. >> >> #define OFPPC10_ALL (OFPPC_PORT_DOWN |