If we do not add a new type of switch, we should write flag to a reg to
indicate the matched packets which are cloned to monitor.
This reg should add to all the pipeline stages of logical switch(both
ingress and egress) to distinguish from normal flow. Is this right for
Russell's point?
If we
-Original Message-
From: on behalf of Bhanuprakash Bodireddy
Date: Thursday, June 29, 2017 at 3:39 PM
To: "d...@openvswitch.org"
Subject: [ovs-dev] [PATCH v3 6/6] dpif-netdev: Flush the packets
-Original Message-
From: on behalf of Bhanuprakash Bodireddy
Date: Thursday, June 29, 2017 at 3:39 PM
To: "d...@openvswitch.org"
Subject: [ovs-dev] [PATCH v3 4/6] netdev-dpdk: Add intermediate
Hi Bhanu
Would it be possible to combine patches 1 and 2, rather than initially defining
an empty
netdev_txq_flush for dpdk ? I think the combined patch would have more context.
Darrell
-Original Message-
From: on behalf of Bhanuprakash Bodireddy
From: Paul Blakey
Always implement get_ifindex without checking if offload is
enabled or not as this should not be related. From ovs-dpctl
we cannot tell if offload is enabled or not as other_config is
not being read.
Signed-off-by: Paul Blakey
Not add new logical_mirror_switch, just use logical_switch of course can
capture the use case. But logical_switch pipeline is complex for flow
monitor. Flow monitor should ignore some tables such as port_security, lb
and so on. And also should consider normal function for normal ports. I
think
Signed-off-by: Darrell Ball
---
tests/system-userspace-macros.at | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/tests/system-userspace-macros.at b/tests/system-userspace-macros.at
index 3fc4ef9..f3337f0 100644
--- a/tests/system-userspace-macros.at
strcasestr is not defined for Windows, so implement a version
that could be used on Windows. This is needed for an upcoming
patch.
Signed-off-by: Darrell Ball
Co-authored-by: Ben Pfaff
Signed-off-by: Ben Pfaff
---
lib/string.c| 22
Russell Bryant writes:
> On Fri, Aug 4, 2017 at 1:00 PM, Aaron Conole wrote:
>> After this commit, users may start a dpdk-enabled ovs setup as a
>> non-root user. This is accomplished by exporting the $HOME directory,
>> which dpdk uses to fill in it's