/pipermail/dev/2016-August/077014.html
There is also kernel support in the works, but no recent series has been
posted. It needs changes to support the 802.1ad feature flag referenced
in the threads above. But if there is interest I can post a RFC version
to the dev list.
Eric.
>Hi all
>
>&quo
hen use that separate variable in your Makefiles
but not the rest of configure.
That said, there is an open patch to autoconf to promote gnulib's
gl_WARN_ADD logic into a formal autoconf macro, and that's one of the
remaining things that needs to be merged in before I can release
autocon
;ifcfg-bond3'>
> correct+appropriate?
Seems to work just fine.
> Should I modify the 'ifcfg-eth1' & 'ifcfg-eth5' settings (to prevent> the
> "TRNETLINK" errors [above])?
I've set "ONBOOT=no" for both interfaces and that see
ors [above])? Or are they correct? e.g., Should one of those
settings contain the name of the [virtual] port 'bond3'?
Should the 'ifcfg-bond3' file be renamed? Or is 'ifcfg-bond3'
correct+appropriate?
Should I modify the 'ifcfg-eth1' & 'if
from XXX.YYY.237.1: icmp_seq=3 ttl=64 time=47.6 ms
>
> --- XXX.YYY.237.1 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2049ms
> rtt min/avg/max/mdev = 47.650/51.073/56.724/4.033 ms
Should I destroy the 'bond2' interface and create the bond using O
; ovs_version: "2.3.2"
> [root@xen-2 ~]# ovs-appctl bond/show bond3 > bond3
> bond_mode: active-backup
> bond may use recirculation: no, Recirc-ID : -1
> bond-hash-basis: 0
> updelay: 0 ms
> downdelay: 0 ms
> lacp_status: off
> active slave mac: 00
On Fri, 2014-11-14 at 16:13 +0100, Hannes Frederic Sowa wrote:
> >
> >
> > Thats a lot of clobbers.
>
> Yes, those are basically all callee-clobbered registers for the
> particular architecture. I didn't look at the generated code for jhash
> and crc_hash because I want this code to always be sa
On Fri, 2014-11-14 at 15:06 +0100, Hannes Frederic Sowa wrote:
> In case the arch_fast_hash call gets inlined we need to tell gcc which
> registers are clobbered with. Most callers where fine, as rhashtable
> used arch_fast_hash via function pointer and thus the compiler took care
> of that. In cas
Hi,
Please refer to the "PORTING" file in the openvswitch folder for further
info.
The real product likes PICA8 had announced several switches are based
on OVS v1.10.0.
Best Regards,
Eric Lee
2014-02-09 20:24 GMT+08:00 Adrián Villalba :
> Hi to all the community!
>
> I'
anged.
Best Regards,
Eric Lee
2014/1/15 love you
> Hi
>
> I am working on openflow specifications 1.0, I want to know about port
> down feature.
>
> enum ofp_port_config {
> OFPPC_PORT_DOWN = 1 << 0, /* Port is administratively down. */
>
> Can controller down
Hi,
Please activate the ovs vswitchd to create the pidfile which also using for
snooping.
/usr/sbin/ovs-vswitchd --pidfile --detach
ovs-ofctl snoop /usr/var/run/openvswitch/br0.snoop --detach --pidfile
Best Regards,
Eric Lee
2013/10/29 ��ふ�j <303429...@qq.com>
> Hi,
> N
11 matches
Mail list logo
