From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Quartulli <antonio@openvpn.net>
Cc: Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC 1/1] net: introduce OpenVPN Data Channel Offload (ovpn-dco)
Date: Wed, 3 Aug 2022 08:42:02 -0700 [thread overview]
Message-ID: <20220803084202.4e249bdb@hermes.local> (raw)
In-Reply-To: <52b9d7c9-9f7c-788e-2327-33af63b9c748@openvpn.net>
On Thu, 28 Jul 2022 15:16:10 +0200
Antonio Quartulli <antonio@openvpn.net> wrote:
> Hi Andrew,
>
> On 28/07/2022 15:07, Andrew Lunn wrote:
> > Also, using a mainline driver out of tree is not easy. The code will
> > make use of the latest APIs, and internal APIs are not stable, making
> > it hard to use in older kernels. So you end up with out of tree
> > wrapper code for whatever version of out of tree Linux you decide to
> > support. Take a look at
> >
> > https://github.com/open-mesh-mirror/batman-adv
>
> Yeah, this is exactly what we are already doing.
> We're just trying to keep is as simple as possible for now:
>
> https://github.com/OpenVPN/ovpn-dco/blob/master/linux-compat.h
>
> Thanks for the pointer anyway (I am already deeply inspired by
> batman-adv, as you may imagine ;-)),
>
Kernel submissions for upstream must be standalone, and any infrastructure
that is only used by an out of tree kernel driver will not be accepted.
The version you propose upstream must have no linux-compat wrappers.
Sorry kernel developers don't care or want to be concerned about some
out of tree project.
next prev parent reply other threads:[~2022-08-03 15:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 1:47 [RFC 0/1] Introducing OpenVPN Data Channel Offload Antonio Quartulli
2022-07-19 1:47 ` [RFC 1/1] net: introduce OpenVPN Data Channel Offload (ovpn-dco) Antonio Quartulli
2022-07-19 15:19 ` Andrew Lunn
2022-07-19 15:21 ` Antonio Quartulli
2022-07-19 15:25 ` Andrew Lunn
2022-07-28 7:41 ` Antonio Quartulli
2022-07-28 13:07 ` Andrew Lunn
2022-07-28 13:16 ` Antonio Quartulli
2022-08-03 15:42 ` Stephen Hemminger [this message]
2022-08-03 15:48 ` Antonio Quartulli
2022-08-03 16:19 ` Stephen Hemminger
2022-08-04 7:34 ` Antonio Quartulli
2022-07-28 16:28 ` Jakub Kicinski
2022-07-28 19:16 ` Antonio Quartulli
2022-07-19 15:37 ` Andrew Lunn
2022-07-28 7:44 ` Antonio Quartulli
2022-07-28 13:12 ` Andrew Lunn
2022-08-03 15:31 ` [RFC v2] " Antonio Quartulli
2022-08-12 18:34 ` Sergey Ryazanov
2022-08-12 18:44 ` Stephen Hemminger
2022-08-30 22:35 ` Sergey Ryazanov
2022-08-12 21:05 ` Antonio Quartulli
2022-08-31 3:15 ` Sergey Ryazanov
2022-09-09 20:40 ` Antonio Quartulli
2022-09-13 0:49 ` Sergey Ryazanov
2022-08-03 16:04 ` [RFC 1/1] " Joe Perches
2022-08-04 7:35 ` Antonio Quartulli
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=20220803084202.4e249bdb@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=antonio@openvpn.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).