-
Notifications
You must be signed in to change notification settings - Fork 63
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
Positive RDMA / smb-direct „taskman test“ between Win-client and linux-Server? #488
Comments
Have you ever searched RDMA or smb-direct work in ISSUE of cifsd-team github? cifsd-team#542
You should add "server multi channel support = yes" parameter in [global] section of your ksmbd.conf If it still doesn't work, please let me know. |
Thank you for the input. Yes, I had a look at various posts but still could not get it to work. Another one I found interesting but also without success: https://forum.level1techs.com/t/how-can-i-help-with-the-new-truenas-100g-testing/179052/8 As to my ksmbd.conf, it already has/had "server multi channel support = yes". On the windows client I tracked RDMA activity with Perfmon. It apparently tries to establish RDMA connections, but they fail. The only time I see any smb_direct messages in dmesg is immediately after start of the service: |
Is there any error messages from ksmbd: smb_direct: ? This message("ksmbd: smb_direct: init RDMA listener. cm_id=0000000084cd3fdd") is the last one ? |
Hi!
Since I am struggling and cannot get it to work: has anyone successfully tested RDMA/smb-direct between a linux ksmbd server and a windows client, so that the windows taskmanager on the client does not show corresponding load (load between windows machine is zero or at least very low (kb/s)) while copying large files (e.g. 30GB) at much higher speeds of 1-2.5GB/s?
If so, could you please give some guidance on hardware, distro, specific steps, settings etc. used?
I have described my tries also here in another thread, but willing to start from scratch if there’s a setup / route more likely / proven to succeed:
#466 (comment)
The text was updated successfully, but these errors were encountered: