Re:User-space RCU
by compudj on Monday August 13, 2018 @10:05AM
(#17750145)
IBM allowed their RCU contribution to be used in LGPLv2 or later code through this commit they kindly contributed to the Userspace RCU project:
commit 54843abcc17c8e8b7600ed635e966c6970d8d20f
Author: Paul E. McKenney <[email protected]>
Date: Sat May 9 01:11:49 2009 -0400
LGPL relicensing of IBM's contributions
Add comments noting IBM's permission to relicense its contributions to the
urcu.h and urcu.c files under the LGPLv2 license, or any later version.
Signed-off-by: Paul E. McKenney <[email protected]>
Reviewed-by: Steven L. Bennett <[email protected]>
Re:User-space RCU
by compudj on Monday August 13, 2018 @11:58AM
(#17751038)
GPLv2 provides implicit patent grant in section 6 and section 7. LGPLv2.1 has basically the same content in section 10 and section 11.
IANAL, but AFAIU LGPLv2.1 provides implicit patent grant in the same way as GPLv2.
IBM has allowed use of RCU in GPL code through its contributions to the Linux kernel for many years now. Their contributions to Userspace RCU provide an implicit patent grant in a similar fashion.
Userspace RCU being LGPLv2.1, it allows proprietary applications to link to it, and therefore use RCU through the library APIs, as long as they satisfy LGPLv2.1 requirements.
Re:User-space RCU
by gpderetta on Monday August 13, 2018 @04:52AM
(#17748810)
IIRC, although some variants might have been patented later, the original patent is form the '90s, so as long as an implementation sticks to what it is described there, it should be safe. IANAL and everything.
Proposals for c++ standardization: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p027...
IANAL, but AFAIU LGPLv2.1 provides implicit patent grant in the same way as GPLv2.
IBM has allowed use of RCU in GPL code through its contributions to the Linux kernel for many years now. Their contributions to Userspace RCU provide an implicit patent grant in a similar fashion.
Userspace RCU being LGPLv2.1, it allows proprietary applications to link to it, and therefore use RCU through the library APIs, as long as they satisfy LGPLv2.1 requirements.
https://en.wikipedia.org/wiki/Read-copy-update#Patents
There's a lot of followup patents around optimizations, but it's probably possible to avoid those.