From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: Sergey Matov <smatov@mirantis.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Vxlan in ovs-dpdk
Date: Thu, 16 Mar 2017 12:58:08 +0000 [thread overview]
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361A0E16C@lhreml501-mbb> (raw)
In-Reply-To: <CAPykWKH9JbAAo5vpqY42XA3FGfjiXF7CTrb6M3-Uq3skUF2n4g@mail.gmail.com>
Thank you Sergey,
I’ve read the article in the link you’ve attached. I still don’t understand how ARP for the NH is resolved
i.e. the NH is connected via the dpdk interface so how can I know the remote NH mac ?
Best regards
avi
From: Sergey Matov [mailto:smatov@mirantis.com]
Sent: Thursday, 16 March, 2017 11:07 AM
To: Avi Cohen (A)
Subject: Re: [dpdk-users] Vxlan in ovs-dpdk
Hello Avi.
OVS+DPDK supports vxlan tunneling in userspace. Packets are not reaching kernel. This requires endpoint IP rule being added to vxlan port.
More details can be found in related article https://github.com/openvswitch/ovs/blob/master/Documentation/howto/userspace-tunneling.rst.
As for OpenStack, Neutron needs endpoint IP to be set up in system. You can find appropriate implementation using https://github.com/openstack/networking-ovs-dpdk plugin for devstack or using Mirantis OpenStack based on Fuel.
2017-03-16 12:47 GMT+04:00 Avi Cohen (A) <avi.cohen@huawei.com<mailto:avi.cohen@huawei.com>>:
Hello,
Does the ovs-dpdk dupports vxlan in user-space ?
If yes what about arp and ip-fwding ? this requires ip-stack (unless you implement this over the dpdk)
But ovs-dpdk is entirely running in user-space. Can someone explain ?
Best regards
avi
--
Best Regards
Sergey Matov
Mirantis Inc
prev parent reply other threads:[~2017-03-16 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 8:47 Avi Cohen (A)
[not found] ` <CAPykWKH9JbAAo5vpqY42XA3FGfjiXF7CTrb6M3-Uq3skUF2n4g@mail.gmail.com>
2017-03-16 12:58 ` Avi Cohen (A) [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B84047ECBD981D4B93EAE5A6245AA361A0E16C@lhreml501-mbb \
--to=avi.cohen@huawei.com \
--cc=smatov@mirantis.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).