test/raw: remove ioat-specific autotest

Since the rawdev autotest can now be used to test all rawdevs on the
system, there is no need for a dedicated ioat autotest command.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
Reviewed-by: Kevin Laatz <kevin.laatz@intel.com>
This commit is contained in:
Bruce Richardson 2020-09-10 17:47:16 +01:00 committed by Thomas Monjalon
parent 39f7b298fe
commit 4b3f8119c7
2 changed files with 2 additions and 20 deletions

View File

@ -55,23 +55,3 @@ test_rawdev_selftests(void)
}
REGISTER_TEST_COMMAND(rawdev_autotest, test_rawdev_selftests);
static int
test_rawdev_selftest_ioat(void)
{
const int count = rte_rawdev_count();
int i;
for (i = 0; i < count; i++) {
struct rte_rawdev_info info = { .dev_private = NULL };
if (rte_rawdev_info_get(i, &info, 0) == 0 &&
strstr(info.driver_name, "ioat") != NULL)
return rte_rawdev_selftest(i) == 0 ?
TEST_SUCCESS : TEST_FAILED;
}
printf("No IOAT rawdev found, skipping tests\n");
return TEST_SKIPPED;
}
REGISTER_TEST_COMMAND(ioat_rawdev_autotest, test_rawdev_selftest_ioat);

View File

@ -213,6 +213,8 @@ API Changes
using the ``rawdev_autotest`` command in the ``dpdk-test`` binary. This
command now calls the self-test function for each rawdev found on the
system, and does not require a specific command per device type.
Following this change, the ``ioat_rawdev_autotest`` command has been
removed as no longer needed.
* stack: the experimental tag has been dropped from the stack library, and its
interfaces are considered stable as of DPDK 20.11.