-
Notifications
You must be signed in to change notification settings - Fork 64
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
should use max_qb_init_rd_atom for initiator_depth? #497
Comments
You need to explain the difference between the two values and say why they should change. |
I don't know clearly. I posted here for your help. I met some Later I noticed that, in ksmbd,
This change did not solve my problem. I eventually upgraded my kernel to make it working. Maybe it is a bug of But this change also did not harm my setup, i.e. it seems correct. So, is it correct? I am not an expert of RDMA.... |
Yes, RDMA of cifs client is broken. Okay, Can you make the patch and submit a patch to the mailing list ([email protected]) ? |
Sure, I'll try it later. |
I am debugging some problems around ksmbd rdma. While this is unrelated, But I noticed that
conn_param.initiator_depth
is set tomax_qb_rd_atom
.However all other modules seem set it to
max_qb_init_rd_atom
instead?The text was updated successfully, but these errors were encountered: