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

Define and document flow control #69

Closed
shefty opened this issue Sep 9, 2014 · 2 comments
Closed

Define and document flow control #69

shefty opened this issue Sep 9, 2014 · 2 comments
Assignees
Milestone

Comments

@shefty
Copy link
Member

shefty commented Sep 9, 2014

There needs to be a mechanism for applications to enable/disable flow control, along with events defined when flow control or buffer overruns occur.

@shefty shefty added this to the alpha release milestone Sep 9, 2014
@shefty
Copy link
Member Author

shefty commented Sep 17, 2014

Flow control is an endpoint attribute or capability. The reporting of a flow control issue would likely go to the control EQ. The behavior of having versus not having flow control needs to be defined based on the endpoint type. The DGRAM EP would likely not use flow control. The MSG EP may or may not. If flow control is not enabled, the behavior needs to be defined -- possibly resulting in the EP failing. The behavior of an RDM EP is more difficult to define.

@shefty
Copy link
Member Author

shefty commented Oct 1, 2014

There may be different levels of flow control. E.g. IB only supports flow control based on receive buffers, not CQ space. With RDM endpoints, flow control may need to take CQ space into consideration. An app may need to be aware of what level of flow control is supported and when flow control overruns a the local CQ, remote CQ, remote receive buffers, etc.

@shefty shefty self-assigned this Dec 9, 2014
@shefty shefty closed this as completed Jan 6, 2015
bturrubiates pushed a commit to bturrubiates/libfabric that referenced this issue Apr 7, 2015
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