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

prov/efa: fixing bug with reporting cq errors and fixing logic #5685

Merged
merged 1 commit into from
Mar 10, 2020

Conversation

dancejic
Copy link
Contributor

this patch fixed a bug where efa_ep_progress_internal would check for
FI_EAVAIL instead of -FI_EAVAIL and fixed some of the logic surrounding error
detection on the function. EQ entries are now filled when the cq cannot be
read or when error entries cannot be read.

Signed-off-by: Nikola Dancejic [email protected]

@dancejic
Copy link
Contributor Author

bot:aws:retest

@wzamazon
Copy link
Contributor

wzamazon commented Mar 3, 2020

bot:as:retest

@wzamazon
Copy link
Contributor

wzamazon commented Mar 3, 2020

bot:aws:retest

1 similar comment
@dancejic
Copy link
Contributor Author

dancejic commented Mar 3, 2020

bot:aws:retest


err = efa_cq_readerr(&cq->cq_fid, &cq_err_entry, flags);
if (OFI_UNLIKELY(err < 0)) {
EFA_WARN(FI_LOG_CQ, "unable to read error entry errno: %ld\n", ret);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ret should be err here

this patch fixed a bug where efa_ep_progress_internal would check for
FI_EAVAIL instead of -FI_EAVAIL and fixed some of the logic surrounding error
detection on the function. EQ entries are now filled when the cq cannot be
read or when error entries cannot be read.

Signed-off-by: Nikola Dancejic <[email protected]>
@rajachan rajachan added this to the release 1.10.0 milestone Mar 10, 2020
@rajachan rajachan merged commit 4dffe5f into ofiwg:master Mar 10, 2020
@dancejic dancejic deleted the cq branch February 1, 2021 08:25
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.

4 participants