Typically, kernel datapath threads send upcalls to userspace where
handler threads process the upcalls. For TAP and DPDK devices, the
datapath threads operate in userspace, so there is no need for
separate handler threads.
This patch allows userspace datapath threads to directly call the
ofproto u
Hi Ben,
enjoy your vacation.
I realise I've posted a lot of patches recently.
If you wish to prioritise any of them please choose
MPLS and recirculation.
On Mon, Jun 16, 2014 at 10:21:46AM -0700, Ben Pfaff wrote:
> Thanks a lot, Simon. I'm on vacation this week so I imagine that this and
> the E
Typically, kernel datapath threads send upcalls to userspace where
handler threads process the upcalls. For TAP and DPDK devices, the
datapath threads operate in userspace, so there is no need for
separate handler threads.
This patch allows userspace datapath threads to directly call the
ofproto u
Dear representative,
I checked on the vtep.xml file under the openvswitch/vtep directory.
There is a "last_error" tab saying that it will show "A human-readable
description of the last error on the connection to the manager;"
When we dig into the code, it really does not make sense. can y
When deleting a mask from the mask array, we always move the last entry
into its current location. Another approach can be NULL in its
current place, and periodically compact it.
The approach taken by this patch is more efficient during run
time. During look up, fast path packet don't have to ski
Simplify flow mask cache replacement without using expensive atomic
memory access to the mask pointers.
Signed-off-by: Andy Zhou
---
datapath/flow_table.c | 44 +---
1 file changed, 21 insertions(+), 23 deletions(-)
diff --git a/datapath/flow_table.c b/da
>
> warning: 1 line adds whitespace errors.
>
Fixed
>
> On Wed, Jun 11, 2014 at 2:24 PM, Andy Zhou wrote:
>> When deleting a mask from the mask array, we always move the last entry
>> into its current location. Another approach can be NULL in its current
>> place, and periodically compact it.
>>
>
You are right. Current bond implementation is based on earlier OVS
that only supports openflow version 1.0 and 1.1.
As you have pointed out, now that group is supported, it is feasible
to leverage the group facility to implement bond.
Do you have more detailed suggestions or implementation to co
Thanks so much, Flavio. Your suggestions helped a lot in my debugging.
It turned out that Docker/LXC was messing up with source address setting
via "ip route change" on Ubuntu 14.04. After uninstalling Docker/LXC, it
worked.
Thanks
Changbin
On Fri, Jun 6, 2014 at 1:49 PM, Flavio Leitner wrot
Hi All,
I have a query on LAG (Bonding) support in OpenVswitch.
Is the LAG implementation in OVS not based on Group tables?
I see that LAG (Bond) interface creation in OVS happens through
non-OpenFlow means and not through an "select" group entry.
Thanks,
Raghu
_
Thanks a lot, Simon. I'm on vacation this week so I imagine that this and
the EXT-187 series will suffer some delay in review.
On Jun 15, 2014 7:33 PM, "Simon Horman" wrote:
> This purpose of this patchset is to provide support for multipart requests
> with more than one part. It does so in three
rte_eal_init() returns the number of parsed dpdk arguments to skip.
dpdk_init() should add 1 to that number, because it has already skipped the
"--dpdk" argument itself
Signed-off-by: Daniele Di Proietto
---
lib/netdev-dpdk.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/
GLЬCKWЬNSCHE NOCH EINMAL VON DEN MITGLIEDERN UND STAB DER LOTTERIE BORD
GOOGLE UK Inc.,
1-13 ST GILES HIGH STREET,
13 matches
Mail list logo
