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

vmbus_client: use existing mesh channels to send revoke #637

Merged
merged 1 commit into from
Jan 16, 2025

Conversation

jstarks
Copy link
Member

@jstarks jstarks commented Jan 9, 2025

In the vmbus client, instead of sending a revoke over the general notify channel (which is hard to multiplex between multiple users of the vmbus client), notify a user of a revoke by closing the per-channel notification channel.

This is the last non-offer use of the notify channel. Change the notify channel to just an offer channel.

@jstarks jstarks requested review from a team as code owners January 9, 2025 17:09
@jstarks jstarks force-pushed the vmbus_client_cleanup_3 branch from 9d1db38 to 65676df Compare January 9, 2025 19:11
SvenGroot
SvenGroot previously approved these changes Jan 10, 2025
In the vmbus client, instead of sending a revoke over the general notify
channel (which is hard to multiplex between multiple users of the vmbus
client), notify a user of a revoke by closing the per-channel
notification channel.

This is the last non-offer use of the notify channel. Change the notify
channel to just an offer channel.
@jstarks jstarks merged commit 7fca23f into microsoft:main Jan 16, 2025
25 checks passed
@jstarks jstarks deleted the vmbus_client_cleanup_3 branch January 16, 2025 21:02
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 this pull request may close these issues.

3 participants