From: Pravin Shelar <pravin.ovn@gmail.com>
To: Harald Welte <laforge@gnumonks.org>
Cc: Jonas Bonn <jonas@norrbonn.se>, Jakub Kicinski <kuba@kernel.org>,
Pravin B Shelar <pbshelar@fb.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [PATCH net-next v5] GTP: add support for flow based tunneling API
Date: Sun, 17 Jan 2021 12:55:45 -0800 [thread overview]
Message-ID: <CAOrHB_BQ1e5eV6qCNmHcQ7UPcrOuBwJC+hLpQ6sxa6+FUO9=Kw@mail.gmail.com> (raw)
In-Reply-To: <YARW4DN9qxOZ7b25@nataraja>
On Sun, Jan 17, 2021 at 7:31 AM Harald Welte <laforge@gnumonks.org> wrote:
>
> Hi Jonas, Jakub and others,
>
> On Sun, Jan 17, 2021 at 02:23:52PM +0100, Jonas Bonn wrote:
> > This patch hasn't received any ACK's from either the maintainers or anyone
> > else providing review. The following issues remain unaddressed after
> > review:
>
> [...]
>
> Full ACK from my point of view. The patch is so massive that I
> as the original co-author and co-maintainer of the GTP kernel module
> have problems understanding what it is doing at all. Furthermore,
> I am actually wondering if there is any commonality between the existing
> use cases and whatever the modified gtp.ko is trying to achieve. Up to
> the point on whether or not it makes sense to have both functionalities
> in the same driver/module at all
>
This is not modifying existing functionality. This patch is adding LWT
tunneling API. Existing functionality remains the same. Let me know if
you find any regression. I can fix it.
LWT is a well known method to implement scalable tunneling which most
of the tunneling modules (GENEVE, GRE, VxLAN etc..) in linux kernel
already supports.
If we separate out gtp.ko. from its LWT implementation, we will need
to duplicate a bunch of existing code as well as code that Jonas is
adding to improve performance using UDP tunnel offloading APIs. I
don't think that is the right approach. Existing tunneling modules
also use the unified module approach to implement traditional and LWT
based tunnel devices.
> > I'm not sure what the hurry is to get this patch into mainline. Large and
> > complicated patches like this take time to review; please revert this and
> > allow that process to happen.
>
> Also acknowledged and supported from my side.
>
> --
> - Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
> ============================================================================
> "Privacy in residential applications is a desirable marketing option."
> (ETSI EN 300 175-7 Ch. A6)
next prev parent reply other threads:[~2021-01-17 20:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-10 7:00 [PATCH net-next v5] GTP: add support for flow based tunneling API Pravin B Shelar
2021-01-13 15:25 ` Pravin Shelar
2021-01-17 0:46 ` Jakub Kicinski
2021-01-17 13:23 ` Jonas Bonn
2021-01-17 15:25 ` Harald Welte
2021-01-17 20:55 ` Pravin Shelar [this message]
2021-01-17 20:47 ` Pravin Shelar
2021-01-18 17:27 ` Jakub Kicinski
2021-01-18 18:27 ` Jonas Bonn
2021-01-18 18:56 ` Jakub Kicinski
2021-01-18 20:01 ` Harald Welte
2021-01-17 13:40 ` Jonas Bonn
2021-01-17 20:42 ` Pravin Shelar
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='CAOrHB_BQ1e5eV6qCNmHcQ7UPcrOuBwJC+hLpQ6sxa6+FUO9=Kw@mail.gmail.com' \
--to=pravin.ovn@gmail.com \
--cc=jonas@norrbonn.se \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=pbshelar@fb.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).