Description of problem: perftest refuses to operate with a not helpful error: "new post send flow is not supported" Version-Release number of selected component (if applicable): perftest-4.4-2.fc31.x86_64 How reproducible: always Steps to Reproduce: ib_read_bw # or any other test Actual results: --------------------------------------------------------------------------------------- new post send flow is not supported Expected results: ************************************ * Waiting for client to connect... * ************************************ Additional info: Older version perftest-4.2-5.fc31.x86_64 worked, building from git master also works.
perftest-4.4/src/perftest_parameters.c 905 static void force_dependecies(struct perftest_parameters *user_param) 906 { ..... 1241 if (!user_param->use_old_post_send) 1242 { 1243 #ifndef HAVE_IBV_WR_API 1244 printf(RESULT_LINE); 1245 fprintf(stderr, " new post send flow is not supported\n"); 1246 exit(1); 1247 #endif 1248 } The new post send API was introduced into rdma-core by this upstream commit. The first release includes the new post send API is rdma-core-24.0 . ================================================== commit 58ef962809865fe58ef166e97788cc12ce8d4ecc Author: Alex Rosenbaum <alexr> Date: Thu Jan 11 18:59:49 2018 +0200 verbs: Introduce a new post send API ===================================================
(In reply to Attila Fazekas from comment #0) > > Steps to Reproduce: > ib_read_bw # or any other test Use "--use_old_post_send" as a workaround for F31, as rdma-core-20.1-6.fc31 dose not support new post send API. > > Actual results: > ----------------------------------------------------------------------------- > ---------- > new post send flow is not supported > > > Expected results: > > ************************************ > * Waiting for client to connect... * > ************************************ > > > Additional info: > Older version perftest-4.2-5.fc31.x86_64 worked, > building from git master also works.
New post send API is used by default in upstream because it performs better in some cases and supports DC connection type. I'm closing this bug as NOTABUG. Please let me know if you have any concern. Thanks
I got all the relevant packages from the fedora repos, I did not had any incompatible sources. IMHO one of the purpose of using a Linux disto to not have to fight with these kind of incompatibilities, "the stuff tested together" .. The criticized code part (in #1)contains a compile time decision, when I build mine it worked. Is the package built in a proper f31 environment ? Is the 'master' code automatically handles the older rdma lib ? rdma-core-20.1-6.fc31.x86_64 is the rdma core in f31 still. I happy to see DC connection and I also like if something performs better, but as long as I am using only the official f31 stuff, it looks like an incompatible package.
(In reply to Attila Fazekas from comment #4) > I got all the relevant packages from the fedora repos, I did not had any > incompatible sources. > IMHO one of the purpose of using a Linux disto to not have to fight > with these kind of incompatibilities, "the stuff tested together" .. > > The criticized code part (in #1)contains a compile time decision, when I > build mine it worked. Because perftest-4.4-2.fc31 is based on perftest-4.4-0.23.g89e176a.tar.gz, which based on branch rdma-core-dc-support . You compiled the master branch. That is why your build works for you. > Is the package built in a proper f31 environment ? Yes, as it was build with fedpkg. > Is the 'master' code automatically handles the older rdma lib ? No, the change is not merged into master branch yet. > rdma-core-20.1-6.fc31.x86_64 is the rdma core in f31 still. > > > I happy to see DC connection and I also like if something performs better, > but as long as I am using only the official f31 stuff, it looks like an > incompatible package. https://github.com/linux-rdma/perftest/pull/88 Upstream opened this PR to fall back to old API. Can you please test the rdma-core-dc-support branch? If it works, I will build next release of perftest for F31. Otherwise, I will apply a F31 specific patch to make perftest always use _OLD_ API.
https://github.com/linux-rdma/perftest/releases/tag/4.4-0.29 I updated perftest for f31.
FEDORA-2020-96752259de has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-96752259de
FEDORA-2020-9c8ea607cc has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9c8ea607cc
FEDORA-2020-96752259de has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-96752259de` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-96752259de See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-9c8ea607cc has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-9c8ea607cc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-9c8ea607cc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-96752259de has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-9c8ea607cc has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.