From: Or Gerlitz <gerlitz.or@gmail.com>
To: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
Cc: David Miller <davem@davemloft.net>,
Anjali Singhai Jain <anjali.singhai@intel.com>,
Andy Gospodarek <gospo@broadcom.com>,
Michael Chan <michael.chan@broadcom.com>,
Simon Horman <simon.horman@netronome.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
John Fastabend <john.fastabend@gmail.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>, Rony Efraim <ronye@mellanox.com>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: SRIOV switchdev mode BoF minutes
Date: Fri, 13 Apr 2018 23:16:19 +0300 [thread overview]
Message-ID: <CAJ3xEMiDundB9p0CvnQ33mLm=7OvG4Yvd5ASH9uR+TkCd_uJhg@mail.gmail.com> (raw)
In-Reply-To: <bec866ff-2898-72b3-247d-f64189ef6d0f@intel.com>
On Fri, Apr 13, 2018 at 7:49 PM, Samudrala, Sridhar
<sridhar.samudrala@intel.com> wrote:
> On 4/13/2018 1:57 AM, Or Gerlitz wrote:
>>> in overlay networks scheme, the uplink rep has the VTEP ip and is not connected
>>> to the bridge, e.g you use ovs you have vf reps and vxlan ports connected
>>> to ovs and the ip stack routes through the uplink rep
> This changes the legacy mode behavior of configuring vtep ip on the pf
> netdev. How does host to host traffic expected to work when vtep ip is moved to uplink rep?
What do you mean host to host traffic, is that two VFs on the same host?
control plane SWs (such as OVS) don't apply encapsulation within the same host
>>>> What about pf-rep?
> Are you planning to create a pf-rep too? Is pf also treated similar to vf in
> switchdev mode?
> All pf traffic goes to pf-rep and pf-rep traffic goes to pf by default
> without any rules programmed?
@ the sriov switchdev ARCH level, pf/pf-rep would work indeed as you described.
We will have pf rep for smartnic schemes where the the pf on the host
is not the manager of the eswitch but rather the smartnic driver instance.
on non smart env, there are some challenges to address for the pf
nic to be fully functional for the slow path (what you described), we
will get there down the road if there is a real need.
next prev parent reply other threads:[~2018-04-13 20:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 19:49 SRIOV switchdev mode BoF minutes Or Gerlitz
2017-11-12 20:38 ` Alexander Duyck
2017-11-13 6:16 ` Or Gerlitz
2017-11-13 17:10 ` Alexander Duyck
2017-11-14 16:44 ` Or Gerlitz
2017-11-14 20:00 ` Alexander Duyck
2017-11-14 21:50 ` Or Gerlitz
2017-11-14 23:05 ` Alexander Duyck
2017-11-14 23:36 ` Jakub Kicinski
2017-11-15 3:04 ` Alexander Duyck
2017-11-15 4:02 ` Jakub Kicinski
2017-11-15 18:25 ` Alexander Duyck
2017-11-16 17:41 ` Or Gerlitz
2017-11-16 18:20 ` Alexander Duyck
2017-11-14 23:32 ` Jakub Kicinski
2018-04-12 17:05 ` Samudrala, Sridhar
2018-04-12 20:20 ` Or Gerlitz
2018-04-12 20:33 ` Samudrala, Sridhar
2018-04-13 8:56 ` Or Gerlitz
2018-04-13 8:57 ` Or Gerlitz
2018-04-13 16:49 ` Samudrala, Sridhar
2018-04-13 20:16 ` Or Gerlitz [this message]
2018-04-13 23:03 ` Samudrala, Sridhar
2018-04-15 6:01 ` Or Gerlitz
2018-04-16 12:39 ` Andy Gospodarek
2018-04-17 2:08 ` Samudrala, Sridhar
2018-04-17 13:30 ` Andy Gospodarek
2018-04-17 13:58 ` Or Gerlitz
2018-04-17 14:47 ` Andy Gospodarek
2018-04-17 16:46 ` Samudrala, Sridhar
2018-04-17 16:53 ` Andy Gospodarek
2018-04-17 23:19 ` Jakub Kicinski
2018-04-18 15:15 ` Andy Gospodarek
2018-04-18 16:26 ` Jakub Kicinski
2018-04-18 17:25 ` Andy Gospodarek
2018-04-18 17:07 ` Parikh, Neerav
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='CAJ3xEMiDundB9p0CvnQ33mLm=7OvG4Yvd5ASH9uR+TkCd_uJhg@mail.gmail.com' \
--to=gerlitz.or@gmail.com \
--cc=anjali.singhai@intel.com \
--cc=davem@davemloft.net \
--cc=gospo@broadcom.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=john.fastabend@gmail.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=ronye@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=simon.horman@netronome.com \
--cc=sridhar.samudrala@intel.com \
/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).