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

Test AWS CI #10097

Closed
wants to merge 17 commits into from
Closed

Test AWS CI #10097

wants to merge 17 commits into from

Conversation

shijin-aws
Copy link
Contributor

No description provided.

@shijin-aws shijin-aws marked this pull request as draft June 17, 2024 23:40
@shijin-aws shijin-aws force-pushed the zcpy_v3 branch 3 times, most recently from fa4b0fe to d1c04d2 Compare June 19, 2024 18:48
This bit is interpreted as a feature on the sender side,
and a request on the receiver side. When zero copy mode
is turned on, sender can choose to send data to receiver's
user recv QP without hdr to optimize performance.
For receiver, when zero-copy mode is enabled, it can only
get pkts delivered to the user recv QP.

Signed-off-by: Shi Jin <[email protected]>
It is only valid when (extra_info[0] & EFA_RDM_EXTRA_FEATURE_USER_RECV_QP) is non-zero

Signed-off-by: Shi Jin <[email protected]>
With user recv pkts posted to separate QP, we don't
need to worry about zero copy recv when posting
internal rx pkts.

Signed-off-by: Shi Jin <[email protected]>
Allocate user posted rx pkts from a separate user_rx_pkt_pool.
Posting user recv buffer to user recv QP without prefix.

Signed-off-by: Shi Jin <[email protected]>
This patch refactors the efa_rdm_ep_set_use_zcpy_rx
function for better readability and logging. It
also removes the requirement for FI_MSG_PREFIX

Signed-off-by: Shi Jin <[email protected]>
When zero copy recv is turned on, the ep cannot
handle rtm pkts delivered to the internal bounce buffer,
because the user recv buffer has been posted to the other
QP and we cannot cancel that.

Signed-off-by: Shi Jin <[email protected]>
@shijin-aws shijin-aws closed this Jun 25, 2024
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.

1 participant