Skip to content
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

Closed
hasKeef opened this issue Oct 20, 2016 · 4 comments
Closed

Documentation - ARCCache Patent #31

hasKeef opened this issue Oct 20, 2016 · 4 comments

Comments

@hasKeef
Copy link

hasKeef commented Oct 20, 2016

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

@hasKeef hasKeef changed the title Documentation Documentation - ARCCache Patent Oct 20, 2016
@ben-manes
Copy link

When I looked it up over a year or so ago, these were the patents I found:

  • IBM: 6996676, 7096321, 7058766, 8612689
  • Sun: 7469320

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.

@derekchiang
Copy link

derekchiang commented Mar 14, 2017

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?

@ben-manes
Copy link

That's a question best put to your corporate legal team.

@armon
Copy link
Member

armon commented Feb 1, 2018

The patent is now mentioned in the package docs.

@armon armon closed this as completed Feb 1, 2018
AkihiroSuda added a commit to AkihiroSuda/golang-lru that referenced this issue Nov 15, 2022
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>
BrandonWeng added a commit to sei-protocol/sei-cosmos that referenced this issue Feb 3, 2023
## 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)
codchen pushed a commit to sei-protocol/sei-cosmos that referenced this issue Feb 12, 2023
## 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants