On Wed, Jun 18, 2014 at 6:38 PM, lin shaopeng wrote:
> Hi, everyone
>
> I am experiencing some strange error of my ovs build. I tried google, but
> none of the answer provided can fix this issue. Anyone have the similar
> problem can give
> me a hint, how to solve it or how
Hi, everyone
I am experiencing some strange error of my ovs build. I tried google, but
none of the answer provided can fix this issue. Anyone have the similar
problem can give
me a hint, how to solve it or how to troubleshooting it? Thank you very
much!
The following is the error message I got
On Thu, May 29, 2014 at 12:36 AM, Ben Pfaff wrote:
> On Wed, May 28, 2014 at 12:04 AM, lin shaopeng wrote:
> > Some heads up, we changed our flow idle_timeout to 300, then ran the test
> > again, and got around 6000 packet-in per second.
> > After some investigation, it t
(),
miniflow_equal_in_minimask(), miniflow_get__ ()...
On Tue, May 27, 2014 at 11:02 PM, Ben Pfaff wrote:
> On Mon, May 26, 2014 at 09:55:33PM +0800, lin shaopeng wrote:
> > I am currently running tests to test packet-in performance of OVS
> > (ovs-2.0.1).
> > By starting up a larg
Hi everyone,
I am currently running tests to test packet-in performance of OVS
(ovs-2.0.1).
By starting up a large number of different connections simultaneously,
causing a bunch of packet-in messages sent to the controller. It turns
out that OVS can only handle about 3000 packet-in messages per s
On Fri, Mar 21, 2014 at 12:15 AM, Jesse Gross wrote:
> On Thu, Mar 20, 2014 at 1:25 AM, lin shaopeng wrote:
> > Greetings folks,
> >
> > I am experiencing an issue with openvswitch-2.0.0。And I believe there is
> a
> > deadlock in it。
> >
> > Steps
Greetings folks,
I am experiencing an issue with openvswitch-2.0.0。And I believe there is a
deadlock in it。
Steps to reproduce the issue:
1.Install openvswitch-2.0.0 on a CentOS machine with kernel version 3.0.57。
2.Start up vswitchd and ovsdb。
3.Create bridge and add vxlan port:
# ovs-vsctl ad
