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

RFC: Rework Pinning interface #2963

Closed
kevina opened this issue Jul 10, 2016 · 1 comment
Closed

RFC: Rework Pinning interface #2963

kevina opened this issue Jul 10, 2016 · 1 comment
Assignees
Labels
need/community-input Needs input from the wider community

Comments

@kevina
Copy link
Contributor

kevina commented Jul 10, 2016

In order to finish #2962 I would like to to rework the Pinner interface a bit:

(1) Fix all commands to accept multiple pins at once for to improve performance from O(N*P) to O(P) where P is the number of (possible indirectly) pinned blocks and N is the number of operations to perform related to pinning.

(1.1) Possible provide a function to Walk all pins and perform arbitrary operations on them.

(2) Provide a function/method to verify all pins. That is to report any pins that are missing or recursive pins that are broken.

(3) I am not sure, but using a RWLock seams like an overkill. A simple mutex should be sufficient. All operations should get what they need from the pinner struct and then release the lock rather than holding a RWLock for the entire operation.

Comments?

@kevina kevina self-assigned this Jul 10, 2016
@whyrusleeping whyrusleeping added the need/community-input Needs input from the wider community label Aug 23, 2016
@kevina
Copy link
Contributor Author

kevina commented Aug 24, 2016

This issue is no longer relevant.

@kevina kevina closed this as completed Aug 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/community-input Needs input from the wider community
Projects
None yet
Development

No branches or pull requests

2 participants