From: Stephen Hemminger <stephen@networkplumber.org>
To: "Maglione, Gregorio" <Gregorio.Maglione@city.ac.uk>
Cc: Paolo Abeni <pabeni@redhat.com>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Florian Westphal <fw@strlen.de>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"Rakocevic, Veselin" <Veselin.Rakocevic.1@city.ac.uk>,
"Markus.Amend@telekom.de" <Markus.Amend@telekom.de>,
"nathalie.romo-moreno@telekom.de"
<nathalie.romo-moreno@telekom.de>
Subject: Re: DCCP Deprecation
Date: Wed, 16 Aug 2023 10:15:47 -0700 [thread overview]
Message-ID: <20230816101547.1c292d64@hermes.local> (raw)
In-Reply-To: <CWLP265MB644901EC2B8353A2AA2A813CC915A@CWLP265MB6449.GBRP265.PROD.OUTLOOK.COM>
On Wed, 16 Aug 2023 15:26:07 +0000
"Maglione, Gregorio" <Gregorio.Maglione@city.ac.uk> wrote:
> > Is the scheduling in the kernel? If so yes, it will cause a MP-DCCP not to be accepted.
> > If it is all done in userspace, then it leaves option for someone to reinvent their own open source version.
>
> The protocol works at the kernel level, and has a GPL scheduler and reordering which are the default algorithms. The GitHub implementation includes some non-GPL schedulers and reordering algorithms used for testing, which can be removed if upstreaming.
IANAL
The implementation I looked at on github was in IMHO a GPL violation because it linked GPL
and non GPL code into a single module. That makes it a derived work.
If you put non-GPL scheduler into userspace, not a problem.
If you put non-GPL scheduler into a different kernel module, according to precedent
set by filesystems and other drivers; then it would be allowed. BUT you would need
to only use exported API's not marked GPL. And adding new EXPORT_SYMBOL() only
used by non-GPL code would get rejected. Kernel developers are openly hostile to non-GPL
code and would want any export symbols to be EXPORT_SYMBOL_GPL.
next prev parent reply other threads:[~2023-08-16 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CWLP265MB6449FC7D80FB6DDEE9D76DA9C930A@CWLP265MB6449.GBRP265.PROD.OUTLOOK.COM>
2023-07-10 18:22 ` DCCP Deprecation Kuniyuki Iwashima
2023-07-10 19:01 ` Jakub Kicinski
2023-07-10 20:31 ` Stephen Hemminger
[not found] ` <CWLP265MB6449543ADBE7B64F5FE1D9F8C931A@CWLP265MB6449.GBRP265.PROD.OUTLOOK.COM>
2023-07-11 10:06 ` Paolo Abeni
2023-08-16 9:38 ` Maglione, Gregorio
2023-08-16 15:00 ` Stephen Hemminger
2023-08-16 15:26 ` Maglione, Gregorio
2023-08-16 17:15 ` Stephen Hemminger [this message]
2023-08-18 9:35 ` Maglione, Gregorio
2023-08-18 16:20 ` Stephen Hemminger
2023-08-29 15:17 ` Maglione, Gregorio
2023-08-30 0:38 ` Jakub Kicinski
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=20230816101547.1c292d64@hermes.local \
--to=stephen@networkplumber.org \
--cc=Gregorio.Maglione@city.ac.uk \
--cc=Markus.Amend@telekom.de \
--cc=Veselin.Rakocevic.1@city.ac.uk \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=nathalie.romo-moreno@telekom.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.