Hmm, now that I try it I see that even "valgrind true" reports the
memory error in question, so it's not a problem with OVS. I'll have to
keep looking for that test.
On Fri, Sep 30, 2016 at 09:23:55PM +0100, Stuart Cardall wrote:
> I noticed after running:
>
> make check-valgrind TESTSUITEFLAGS=
On Fri, Sep 30, 2016 at 03:07:17AM +0100, Stuart Cardall wrote:
> The patches improved the failures to 11:
>
> _testsuite: 7 8 761 1859 1860 1861 1862 1863 1864 1868 1870 failed:_
>
> 7: vsctl-bashcomp - basic verification FAILED
> (completion.at:352)
> 8: vsctl-bashcomp - argument co
The patches improved the failures to 11:
_testsuite: 7 8 761 1859 1860 1861 1862 1863 1864 1868 1870 failed:_
7: vsctl-bashcomp - basic verification FAILED
(completion.at:352)
8: vsctl-bashcomp - argument completionFAILED
(completion.at:454)
761: tunnel - Geneve option pre
The FAQ says:
### Q: How do I add support for a new field or header?
A: Add new members for your field to "struct flow" in lib/flow.h, and
add new enumerations for your new field to "enum mf_field_id" in
lib/meta-flow.h, following the existing pattern. Also, add support
to miniflow_extr
On Thu, Sep 29, 2016 at 11:56:14PM -0600, Scott Lowe wrote:
> Please see my response below.
>
>
> > On Sep 29, 2016, at 11:27 PM, Ben Pfaff wrote:
> >
> > On Thu, Sep 29, 2016 at 10:19:18PM -0600, Scott Lowe wrote:
> >> Hi all, I was wondering if someone here could help me debug/troubleshoot
>
On Fri, Sep 30, 2016 at 02:33:21PM +0200, Wolfgang Bumiller wrote:
> I've noticed openvswitch apparently blindly deletes the ingress qdisc
> of bridge ports even if no ingress policing is configured.
> This also prevents the use of this qdisc for purposes other than the
> in OVS implemented ingress
I've noticed openvswitch apparently blindly deletes the ingress qdisc
of bridge ports even if no ingress policing is configured.
This also prevents the use of this qdisc for purposes other than the
in OVS implemented ingress policing (eg. handling fw-marks, bpf based
filters, or early port/address/
Hi,
Currently ingress and egress policing was supported on dpdk ports.
Is there a plan to support egress shaping by creating user-space queues ?
Or currently is there a way to do egress shaping on dpdk netdev interfaces
?
It seems egress shaping does not work on tap/internal-ports/patch port
