-
Notifications
You must be signed in to change notification settings - Fork 300
Issues: linux-rdma/perftest
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Comparison of GPUDirect ( GPU Memory)- NIC access vs Hop Memory GPU-> Host Memory -> NIC
#297
opened Nov 13, 2024 by
alokprasad
Why are rate_limit, burst_size and other parameters designed under "Rate Limiter"?
#294
opened Nov 5, 2024 by
yangrudan
OFED - perftest - perftest_communication.c - rdma_write_keys and rdma_read_keys: Pointer to address bug
#287
opened Sep 5, 2024 by
mobooya
A simple math in the reported number, the MsgRate and #iterations don't match
#273
opened Aug 3, 2024 by
shenweihai1
What is the different between bandwidth testing and lantency testing in RDMA?
#266
opened Jun 8, 2024 by
YuMJie
ib_write_bw works fine without -R. But only very small bandwidth when using -R option
#240
opened Jan 4, 2024 by
chgdragon2023
why set recv_sge_list start addr refer to buf start addr after post the recv wqes of tx-depth
#208
opened May 15, 2023 by
smiceice
infinite ib_write_bw runs do not work when using GPUs on the client side
#68
opened Dec 5, 2019 by
drossetti
memcpy to pointer address instead of pointer location in perftest_communication.c
#55
opened May 14, 2019 by
lonico
ProTip!
Updated in the last three days: updated:>2025-01-05.