Re: [ovs-dev] OVS-DPDK performance problem on ixgbe vector PMD

2015-08-22 Thread Gray, Mark D
> > Hi, > > I've set up a simple packet forwarding perf test on a dual-port 10G > 82599ES: one port receives 64 byte UDP packets, the other sends it out, > one core used. I've used latest OVS with DPDK 2.1, and the first result > was only 13.2 Mpps, which was a bit far from the 13.9 I've seen la

Re: [ovs-dev] [PATCH 2/3] ovsdb-server: Add the ability to push peer-cert.

2015-08-22 Thread Ben Pfaff
On Fri, Aug 21, 2015 at 03:43:18PM -0700, Gurucharan Shetty wrote: > On Fri, Aug 21, 2015 at 2:43 PM, Ben Pfaff wrote: > > On Thu, Aug 20, 2015 at 10:03:39AM -0700, Gurucharan Shetty wrote: > I took all your suggestions and pushed the series. I have one question > for you though. > In lib/stream-s

[ovs-dev] [PATCH] ovn-controller-vtep.at: Remove all 'Broken pipe' warning logs from ovsdb-server.log.

2015-08-22 Thread Alex Wang
This commit makes the OVN_CONTROLLER_VTEP_STOP remove all 'Broken pipe' warning logs from ovsdb-server.log before running 'check_log'. This is in that *ctl command (e.g. ovn-nbctl) exits right after committing the change to database; however, in reaction, some daemon (e.g. ovn-controller-vtep) ma

Re: [ovs-dev] [PATCH] coverage: Add coverage_try_clear() for performance-critical threads.

2015-08-22 Thread Alex Wang
Sorry for the delay of pushing this and related dpdk patches, Want to spend some time next week measuring the performance impact,~ Thanks, Alex Wang, On Fri, Aug 21, 2015 at 12:48 PM, Ben Pfaff wrote: > On Thu, Aug 13, 2015 at 11:48:49AM -0700, Alex Wang wrote: > > For performance-critical thr

[ovs-dev] Returned mail: Data format error

2015-08-22 Thread donmcthy
The original message was received at Sat, 22 Aug 2015 13:25:35 +0300 from 180.117.91.27 - The following addresses had permanent fatal errors - ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] Hi

2015-08-22 Thread sramars
The original message was received at Sat, 22 Aug 2015 16:28:44 +0800 from cisco.com [52.135.128.110] - The following addresses had permanent fatal errors - - Transcript of session follows - while talking to openvswitch.org.: >>> MAIL From:sram...@cisco.com <<< 501 sram...@cisco