From: Bart Van Assche <bart.vanassche@sandisk.com>
To: Doug Ledford <dledford@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: CQ and RDMA READ/WRITE APIs
Date: Tue, 17 May 2016 10:29:49 -0700 [thread overview]
Message-ID: <573B550D.5020008@sandisk.com> (raw)
In-Reply-To: <6633ce02-7983-ad09-f95d-03cea6f54e31@redhat.com>
On 05/16/2016 11:23 AM, Doug Ledford wrote:
> In this particular case, the dual license is used by the OpenFabrics
> Alliance. They strip the RDMA stack in the kernel down to just the RDMA
> stack files and ship those separate from the rest of the kernel, along
> with the necessary user space stuff, and put the entire compilation
> under the same dual GPL/BSD license. That's what their OFED product is.
>
> As I understand it, members of the OFA (Intel, Mellanox, Chelsio, etc.)
> actually signed an agreement as part of their membership entry into OFA
> that they would preserve that dual license when submitting code
> upstream. This was originally intended to make sure that the stack as a
> whole could be used upstream, in distros, on switches, etc. The idea
> being that a unified stack that could be copied around would enhance
> interoperability or something like that.
>
> I can't speak to how actively used it is any more. I think maybe on
> switches or some other dedicated devices. But, I was asked by the OFA
> to try and preserve it.
>
> In this particular case, Christoph wrote his code from scratch. I'm not
> concerned with it. It was never dual licensed and need not be. But he
> did submit patches that modified existing dual license drivers to use
> his new code and removed their own implementation of the same thing in
> the process. What used to be more or less functional drivers that could
> be copied and used elsewhere will no longer be able to be copied in the
> same way. I'm just waiting for Sagi Grimberg to speak for iSER and for
> Bart van Assche to speak for SRP and let me know that they are OK with
> the change. I think a patch set that will essentially change the
> licensing nature of their code should carry their explicit approval of
> the license change.
(+linux-rdma)
Hello Doug,
As far as I know SanDisk, a Western Digital Company, is fine with
changing the license of the code under drivers/infiniband/ulp/srpt from
dual licensed into GPL-only. However, if OFA members want that the
entire RDMA core is dual licensed I think we will have to talk to Tejun:
$ PAGER= git grep EXPORT_SYMBOL_GPL drivers/infiniband/
drivers/infiniband/core/device.c:EXPORT_SYMBOL_GPL(ib_wq);
$ git show f06267104dd9112f11586830d22501d0e26245ea
commit f06267104dd9112f11586830d22501d0e26245ea
Author: Tejun Heo <tj@kernel.org>
Date: Tue Oct 19 15:24:36 2010 +0000
RDMA: Update workqueue usage
[ ... ]
+struct workqueue_struct *ib_wq;
+EXPORT_SYMBOL_GPL(ib_wq);
[ ... ]
$ PAGER= git grep -lw ib_wq drivers/infiniband/
drivers/infiniband/core/cache.c
drivers/infiniband/core/device.c
drivers/infiniband/core/roce_gid_mgmt.c
drivers/infiniband/core/sa_query.c
drivers/infiniband/core/umem.c
drivers/infiniband/hw/qib/qib_iba7220.c
drivers/infiniband/hw/qib/qib_iba7322.c
drivers/infiniband/hw/qib/qib_init.c
Bart.
next prev parent reply other threads:[~2016-05-17 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <743399f9-10b7-6e62-2bf4-6a8656df8a55@redhat.com>
2016-05-16 11:49 ` CQ and RDMA READ/WRITE APIs Christoph Hellwig
2016-05-16 14:51 ` Doug Ledford
2016-05-16 17:46 ` Linus Torvalds
2016-05-16 18:23 ` Doug Ledford
2016-05-17 17:29 ` Bart Van Assche [this message]
2016-05-17 17:32 ` Doug Ledford
2016-05-17 18:50 ` Linus Torvalds
2016-05-18 2:48 ` Parav Pandit
2016-05-18 14:07 ` Doug Ledford
2016-05-18 15:54 ` Parav Pandit
2016-05-17 5:38 ` Christoph Hellwig
2016-05-17 15:35 ` Christoph Lameter
2016-05-16 15:26 ` Doug Ledford
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=573B550D.5020008@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=dledford@redhat.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=sagi@grimberg.me \
--cc=torvalds@linux-foundation.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