Hi Jesse:
I noticed that OVS 2.0.0 stated that OVS switch is now multi-threaded. Is each
thread mapped to an unique queue on the VNIC side? Is it possible to use set
affinity to map ovs switch daemons to a particular set of cores?
Much Thanks
Morgan Yang
From: Jesse Gross [mailto:je...@nicira.
Hello all, I'm relatively new with all of this but I'm hoping that someone may
be able to shed some light.
What I'm trying to accomplish is to have a virtual firewall/router on the same
machine as other virtual guests operating as servers.
I have set up at the moment, Ubuntu KVM host, with 5 gues
Hi Jesse:
The VM’s are staticly mapped to cpu cores. 16 cores total, 2 cores per VM, each
VM is running 2 threads of IPerf (client or server, this is a back to back
connection).
All the CPU’s are running 40~45%. I have hyperthreading disabled, each VM has
2GB of RAM, hypervisor has 32GB of RAM
On Thu, Oct 24, 2013 at 12:44:26AM +, Morgan Yang wrote:
> It is possible to clear port stats via ovs-ofctl?
No.
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
On Wed, Oct 23, 2013 at 6:07 PM, Morgan Yang wrote:
> Hi All:
>
> ** **
>
> I am doing testing with Mellanox’s CX3 40G NIC.
>
> ** **
>
> The setup without OVS runs about 37~38 Gbps between multiple threads of
> IPERF, and no errors are noticed on the Ethernet interfaces
>
> ** **
>
Just to elaborate, I don't think the physical interface is a bottleneck, but I
think because OVS can't switch packets fast enough between the virual QUEUE's,
the physical interface is now the one dropping packets.
From: discuss-boun...@openvswitch.org [mailto:discuss-boun...@openvswitch.org]
On
Hi All:
It is possible to clear port stats via ovs-ofctl?
Much Thanks
Morgan Yang
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
On Wed, Oct 23, 2013 at 08:17:35PM -0200, Lucas Brasilino wrote:
> Hi Ben
>
> >> Any special reason for that ?
> >
> > Different sockets need different names?
>
> Maybe I'm misunderstanding something, but as far I have noticed, they
> use this unix domain socket to communicate with each other.
>
Thank you Ben, I was also thinking that but was not sure as I am still trying
to understand flows.
> On Oct 23, 2013, at 6:00 PM, Ben Pfaff wrote:
>
> Would your per-VLAN flows have the same actions as the single flows
> you showed below? If so, the there is no benefit to per-VLAN flows.
>
>
Would your per-VLAN flows have the same actions as the single flows
you showed below? If so, the there is no benefit to per-VLAN flows.
On Wed, Oct 23, 2013 at 05:35:52PM -0500, Faisal Ali wrote:
> Sorry for being unclear. The broadcast flow defined below was
> originally applied to the bridge it
Sorry for being unclear. The broadcast flow defined below was originally
applied to the bridge itself.
Now I am adding vlans to the bridge, so my confusion is whether I have to
define (adding vlan tag) this flow per vlan or will this flow definition
suffice for all the vlans in the test bridge
Hi Ben
>> Any special reason for that ?
>
> Different sockets need different names?
Maybe I'm misunderstanding something, but as far I have noticed, they
use this unix domain socket to communicate with each other.
ovs-vsctl and ovs-vswitchd connect()'s to /db.sock
while ovsdb-server listen()'s to
I don't know what you're trying to accomplish but "normal" understands
and honors VLANs.
On Wed, Oct 23, 2013 at 02:15:29PM -0500, Faisal Ali wrote:
> Thank you Ben,
>
> If I have many vlans will this same flow work for all vlans in the test
> bridge or do I have to define the flow per vlan
>
>
Thank you Ben,
If I have many vlans will this same flow work for all vlans in the test bridge
or do I have to define the flow per vlan
ovs-ofctl add-flow test-br 'priority=1900 in_port=13
dl_dst='ff:ff:ff:ff:ff:ff' actions='normal''
ovs-ofctl add-flow test-br 'priority=1900 in_port=13 nw_dst='22
On Tue, Oct 22, 2013 at 11:22 PM, Sukyoung Oh wrote:
> I appreciate for your answer. thank you for your attention.
>
> As I mentioned before, I am trying to use the openvswitch on DomU domain. (I
> am using Xen)
>
> specifically, my intent is to control the flows that come into DomU from
> VFs(SR-
On Wed, Oct 23, 2013 at 10:36:50AM -0200, Lucas Brasilino wrote:
> ovsdb-server uses $PREFIX/var/run/openvswitch/ovsdb-server.$PID.ctl as
> its default unix domain socket (maybe default file name on Linux),
> while ovs-vsctl and ovs-vswitchd uses
> $PREFIX/var/run/openvswitch/db.sock.
>
> Any spec
On Wed, Oct 23, 2013 at 09:49:35AM +, Huimin She wrote:
> Does anyone know about the multicore support in OVS?
Yes.
> Is it possible to bind a bridge/port (or whatever) to a specific CPU
> core or multiple cores?
No.
___
discuss mailing list
discus
Lucas, thanks, I will try that
--
Nan
On Tuesday, October 22, 2013 at 4:46 PM, Lucas Brasilino wrote:
> Hi!
>
> > I want the VMs not only be able to communicate with each other, but also can
> > access Internet through 192.168.55.1
> > what shall I do?
> >
>
>
> I haven't tested this set
Hi
ovsdb-server uses $PREFIX/var/run/openvswitch/ovsdb-server.$PID.ctl as
its default
unix domain socket (maybe default file name on Linux), while ovs-vsctl
and ovs-vswitchd
uses $PREFIX/var/run/openvswitch/db.sock.
Any special reason for that ?
Att
Lucas Brasilino
MSc Student @ Federal Universi
Hi,
Does anyone know about the multicore support in OVS?
Is it possible to bind a bridge/port (or whatever) to a specific CPU core or
multiple cores?
Thanks.
Best regards,
Huimin She
___
discuss mailing list
discuss@openvswitch.org
http://openvswitch.
20 matches
Mail list logo
