-
Notifications
You must be signed in to change notification settings - Fork 62
Adding maxSpinCount to port channel flush #518
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
Conversation
/azp run |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR fixes issue #482 by adding a configurable maxSpinCount parameter to flush-related functions.
- Updated the putWithSignalAndFlush methods in both BasePortChannelDeviceHandle and PortChannelDeviceHandle to accept a maxSpinCount parameter.
- Updated the flush method to use the new maxSpinCount parameter.
Comments suppressed due to low confidence (1)
include/mscclpp/port_channel_device.hpp:149
- Please update the function documentation to describe the new 'maxSpinCount' parameter and its expected impact on flush behavior.
MSCCLPP_DEVICE_INLINE void putWithSignalAndFlush(MemoryId dst, uint64_t dstOffset, MemoryId src, uint64_t srcOffset, uint64_t size, int64_t maxSpinCount = 1000000) {
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fix #482