-
Notifications
You must be signed in to change notification settings - Fork 500
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation - ARCCache Patent #31
Comments
When I looked it up over a year or so ago, these were the patents I found:
Sun released their implementation under the CDDL for ZFS, which makes it unclear if that protects from claims from IBM's earlier patents. I filled a request for clarification of OSS usage from IBM's patent team, but declined to pursue it when they responded (something like) 9 months later. |
Sorry if this is a naive question, but does this mean that we can't use this library in our OSS projects? What about in commercial projects? |
That's a question best put to your corporate legal team. |
The patent is now mentioned in the package docs. |
This commit ensures that the patented files are not compiled in, so that consumers do not need to validate that the patented files are not actually used. Consumers can still opt-in to use the patented files by copying them. Fix hashicorp#31 Fix hashicorp#73 Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
## Describe your changes and provide context IRRC we had discussions around bumping the limit for the inter-block cache since 1k is pretty little for our volume of TXs per block. Im setting it to 100k to be the same as the BoundedCacheKv store While I was investigating the race condition issue in the LRU cache, I saw that several repos brought up concerns around using ArcCache in their code as it's been patented by IBM (and later sold to Intel) hashicorp/golang-lru#31 hashicorp/golang-lru#73 ipfs/kubo#6590 ipfs/go-ipfs-blockstore#20 Postgres and IPFS replaced it with 2Q, which based on the whitepaper should have the same performance as ARC. ## Testing performed to validate your change Deployed a LT cluster with these changes and saw no impact to consensus and the performance (with LT clients running) is similar ![image](https://user-images.githubusercontent.com/18161326/216499319-be5ae693-242f-453c-8073-414bf5f810bd.png)
## Describe your changes and provide context IRRC we had discussions around bumping the limit for the inter-block cache since 1k is pretty little for our volume of TXs per block. Im setting it to 100k to be the same as the BoundedCacheKv store While I was investigating the race condition issue in the LRU cache, I saw that several repos brought up concerns around using ArcCache in their code as it's been patented by IBM (and later sold to Intel) hashicorp/golang-lru#31 hashicorp/golang-lru#73 ipfs/kubo#6590 ipfs/go-ipfs-blockstore#20 Postgres and IPFS replaced it with 2Q, which based on the whitepaper should have the same performance as ARC. ## Testing performed to validate your change Deployed a LT cluster with these changes and saw no impact to consensus and the performance (with LT clients running) is similar ![image](https://user-images.githubusercontent.com/18161326/216499319-be5ae693-242f-453c-8073-414bf5f810bd.png)
In the documentation for ARCCache it says that the algorithm is patented by IBM
It looks like IBM sold (or traded or gave) the patent to Intel in 2013
https://assignment.uspto.gov/patent/index.html#/patent/search/resultAbstract?id=6996676&type=patNum
http://legacy-assignments.uspto.gov/assignments/assignment-pat-30228-415.pdf
The text was updated successfully, but these errors were encountered: