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

Move the 'buffered' reading into shared-memory-ring #7

Open
djs55 opened this issue Nov 1, 2014 · 0 comments
Open

Move the 'buffered' reading into shared-memory-ring #7

djs55 opened this issue Nov 1, 2014 · 0 comments

Comments

@djs55
Copy link
Member

djs55 commented Nov 1, 2014

To be able to survive crashes we need to read whole packets into a persistent buffer, which is tricky given that the ring is too small to accommodate a whole packet.

To achieve this we seem to have created a not-very-good circular buffer implementation which is supposed to be layered on top of the quite-decent implementation in shared-memory-ring. Perhaps we should generalise shared-memory-ring to be able to create larger ring buffers.

euanh pushed a commit to xapi-project/ocaml-xenstore that referenced this issue Feb 15, 2016
CA-195461: increase limit of maximum incoming watches to xenstore
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant