From: David Miller <davem@davemloft.net>
To: Yuval.Mintz@qlogic.com
Cc: manish.chopra@qlogic.com, netdev@vger.kernel.org, Ariel.Elior@qlogic.com
Subject: Re: [PATCH v2 net-next 2/5] qed/qede: Add VXLAN tunnel slowpath configuration support
Date: Thu, 14 Apr 2016 16:15:04 -0400 (EDT) [thread overview]
Message-ID: <20160414.161504.381200373149512245.davem@davemloft.net> (raw)
In-Reply-To: <SN2PR11MB0094C4E2F13DA03C1E06C99497970@SN2PR11MB0094.namprd11.prod.outlook.com>
From: Yuval Mintz <Yuval.Mintz@qlogic.com>
Date: Thu, 14 Apr 2016 19:52:44 +0000
>> Why do you call all of these offloads the "slowpath"?
>
> We term by 'slowpath' all the non {data,fast}path configurations,
> I.e., everything that doesn't really involves the ingress/egress handling
> of packets but rather the infrastructure changes surrounding it.
>
> That exactly what we have in this patch - adding the ndo hooks
> necessary for configuring the FW/HW in the proper mode to support
> vxlan tunnels.
>
> Only the last patch in the series is actually adding the fastpath stuff.
Thanks for explaining.
next prev parent reply other threads:[~2016-04-14 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 5:38 [PATCH v2 net-next 0/5] qed/qede: Add tunneling support Manish Chopra
2016-04-14 5:38 ` [PATCH v2 net-next 1/5] qed: Add infrastructure support for tunneling Manish Chopra
2016-04-14 5:38 ` [PATCH v2 net-next 2/5] qed/qede: Add VXLAN tunnel slowpath configuration support Manish Chopra
2016-04-14 19:26 ` David Miller
2016-04-14 19:52 ` Yuval Mintz
2016-04-14 20:15 ` David Miller [this message]
2016-04-14 5:38 ` [PATCH v2 net-next 3/5] qed/qede: Add GENEVE " Manish Chopra
2016-04-14 5:38 ` [PATCH v2 net-next 4/5] qed: Enable GRE tunnel slowpath configuration Manish Chopra
2016-04-14 5:38 ` [PATCH v2 net-next 5/5] qede: Add fastpath support for tunneling Manish Chopra
2016-04-15 21:08 ` [PATCH v2 net-next 0/5] qed/qede: Add tunneling support David Miller
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=20160414.161504.381200373149512245.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Ariel.Elior@qlogic.com \
--cc=Yuval.Mintz@qlogic.com \
--cc=manish.chopra@qlogic.com \
--cc=netdev@vger.kernel.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).