From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>
Subject: |WARNING| pw144121 [PATCH v4 5/5] app/test: add unit tests for soring API
Date: Tue, 17 Sep 2024 14:12:13 +0200 (CEST) [thread overview]
Message-ID: <20240917121213.81DDD121D10@dpdk.org> (raw)
In-Reply-To: <20240917120946.1212-6-konstantin.v.ananyev@yandex.ru>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/144121
_coding style issues_
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#45:
Subject: [PATCH v4 5/5] app/test: add unit tests for soring API
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#68:
Add both functional and stess test-cases for soring API.
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#69:
Stress test serves as both functional and performance test of soring
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#97: FILE: app/test/meson.build:178:
+ 'test_soring.c': [],
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#98: FILE: app/test/meson.build:179:
+ 'test_soring_mt_stress.c': [],
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#99: FILE: app/test/meson.build:180:
+ 'test_soring_stress.c': [],
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#115: FILE: app/test/test_soring.c:7:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#136: FILE: app/test/test_soring.c:28:
+#include <rte_soring.h>
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#142: FILE: app/test/test_soring.c:34:
+#define SORING_TEST_ASSERT(val, expected) do { \
WARNING:SINGLE_STATEMENT_DO_WHILE_MACRO: Single statement macros should not use a do {} while (0) loop
#142: FILE: app/test/test_soring.c:34:
+#define SORING_TEST_ASSERT(val, expected) do { \
+ RTE_TEST_ASSERT(expected == val, \
+ "%s: expected %u got %u
", #val, expected, val); \
+} while (0)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#148: FILE: app/test/test_soring.c:40:
+set_soring_init_param(struct rte_soring_param *prm,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#148: FILE: app/test/test_soring.c:40:
+set_soring_init_param(struct rte_soring_param *prm,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#164: FILE: app/test/test_soring.c:56:
+move_forward_stage(struct rte_soring *sor,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#171: FILE: app/test/test_soring.c:63:
+ acquired = rte_soring_acquire_bulk(sor, acquired_objs, stage,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#173: FILE: app/test/test_soring.c:65:
+ SORING_TEST_ASSERT(acquired, num_packets);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#174: FILE: app/test/test_soring.c:66:
+ rte_soring_release(sor, NULL, stage, num_packets,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#181: FILE: app/test/test_soring.c:73:
+ * struct rte_soring_param param checking.
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#184: FILE: app/test/test_soring.c:76:
+test_soring_init(void)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#186: FILE: app/test/test_soring.c:78:
+ struct rte_soring *sor = NULL;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#187: FILE: app/test/test_soring.c:79:
+ struct rte_soring_param prm;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#193: FILE: app/test/test_soring.c:85:
+ set_soring_init_param(&prm, "alloc_memory", sizeof(uintptr_t),
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#195: FILE: app/test/test_soring.c:87:
+ sz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#197: FILE: app/test/test_soring.c:89:
+ RTE_TEST_ASSERT_NOT_NULL(sor, "could not allocate memory for soring");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#199: FILE: app/test/test_soring.c:91:
+ set_soring_init_param(&prm, "test_invalid_stages", sizeof(uintptr_t),
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#201: FILE: app/test/test_soring.c:93:
+ rc = rte_soring_init(sor, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#202: FILE: app/test/test_soring.c:94:
+ RTE_TEST_ASSERT_FAIL(rc, "initted soring with invalid num stages");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#204: FILE: app/test/test_soring.c:96:
+ set_soring_init_param(&prm, "test_invalid_esize", 0,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#206: FILE: app/test/test_soring.c:98:
+ rc = rte_soring_init(sor, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#207: FILE: app/test/test_soring.c:99:
+ RTE_TEST_ASSERT_FAIL(rc, "initted soring with 0 esize");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#209: FILE: app/test/test_soring.c:101:
+ set_soring_init_param(&prm, "test_invalid_esize", 9,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#211: FILE: app/test/test_soring.c:103:
+ rc = rte_soring_init(sor, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#212: FILE: app/test/test_soring.c:104:
+ RTE_TEST_ASSERT_FAIL(rc, "initted soring with esize not multiple of 4");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#214: FILE: app/test/test_soring.c:106:
+ set_soring_init_param(&prm, "test_invalid_rsize", sizeof(uintptr_t),
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#216: FILE: app/test/test_soring.c:108:
+ rc = rte_soring_init(sor, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#217: FILE: app/test/test_soring.c:109:
+ RTE_TEST_ASSERT_FAIL(rc, "initted soring with rcsize not multiple of 4");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#219: FILE: app/test/test_soring.c:111:
+ set_soring_init_param(&prm, "test_invalid_elems", sizeof(uintptr_t),
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#220: FILE: app/test/test_soring.c:112:
+ RTE_SORING_ELEM_MAX + 1, 1, 4, RTE_RING_SYNC_MT,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#222: FILE: app/test/test_soring.c:114:
+ rc = rte_soring_init(sor, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#223: FILE: app/test/test_soring.c:115:
+ RTE_TEST_ASSERT_FAIL(rc, "initted soring with invalid num elements");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#230: FILE: app/test/test_soring.c:122:
+test_soring_get_memsize(void)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#233: FILE: app/test/test_soring.c:125:
+ struct rte_soring_param prm;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#236: FILE: app/test/test_soring.c:128:
+ set_soring_init_param(&prm, "memsize", sizeof(uint32_t *),
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#238: FILE: app/test/test_soring.c:130:
+ sz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#241: FILE: app/test/test_soring.c:133:
+ set_soring_init_param(&prm, "memsize", sizeof(uint8_t),
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#243: FILE: app/test/test_soring.c:135:
+ sz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'calcuated' may be misspelled - perhaps 'calculated'?
#244: FILE: app/test/test_soring.c:136:
+ RTE_TEST_ASSERT_EQUAL(sz, -EINVAL, "calcuated size incorrect");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#246: FILE: app/test/test_soring.c:138:
+ set_soring_init_param(&prm, "memsize", 0,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#248: FILE: app/test/test_soring.c:140:
+ sz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#256: FILE: app/test/test_soring.c:148:
+test_soring_stages(void)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#258: FILE: app/test/test_soring.c:150:
+ struct rte_soring *sor = NULL;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#259: FILE: app/test/test_soring.c:151:
+ struct rte_soring_param prm;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#271: FILE: app/test/test_soring.c:163:
+ set_soring_init_param(&prm, "stages", sizeof(uint32_t), 32,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#273: FILE: app/test/test_soring.c:165:
+ ssz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'couldn' may be misspelled - perhaps 'could'?
#276: FILE: app/test/test_soring.c:168:
+ RTE_TEST_ASSERT_NOT_NULL(sor, "couldn't allocate memory for soring");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#276: FILE: app/test/test_soring.c:168:
+ RTE_TEST_ASSERT_NOT_NULL(sor, "couldn't allocate memory for soring");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#277: FILE: app/test/test_soring.c:169:
+ rte_soring_init(sor, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#284: FILE: app/test/test_soring.c:176:
+ enqueued = rte_soring_enqueux_burst(sor, objs, rcs, 32, NULL);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#285: FILE: app/test/test_soring.c:177:
+ SORING_TEST_ASSERT(enqueued, 32);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#289: FILE: app/test/test_soring.c:181:
+ dequeued = rte_soring_dequeue_bulk(sor, dequeued_objs,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#292: FILE: app/test/test_soring.c:184:
+ SORING_TEST_ASSERT(dequeued, 0);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#294: FILE: app/test/test_soring.c:186:
+ acquired = rte_soring_acquirx_bulk(sor, acquired_objs,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#296: FILE: app/test/test_soring.c:188:
+ SORING_TEST_ASSERT(acquired, 32);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#299: FILE: app/test/test_soring.c:191:
+ SORING_TEST_ASSERT(acquired_rcs[j], j + stage);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#300: FILE: app/test/test_soring.c:192:
+ SORING_TEST_ASSERT(acquired_objs[j], j + stage + 32);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#306: FILE: app/test/test_soring.c:198:
+ rte_soring_releasx(sor, acquired_objs,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#311: FILE: app/test/test_soring.c:203:
+ dequeued = rte_soring_dequeux_bulk(sor, dequeued_objs, dequeued_rcs,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#313: FILE: app/test/test_soring.c:205:
+ SORING_TEST_ASSERT(dequeued, 32);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#316: FILE: app/test/test_soring.c:208:
+ SORING_TEST_ASSERT(dequeued_rcs[i], i + 10000);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#317: FILE: app/test/test_soring.c:209:
+ SORING_TEST_ASSERT(dequeued_objs[i], i + 32 + 10000);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#324: FILE: app/test/test_soring.c:216:
+test_soring_enqueue_dequeue(void)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#326: FILE: app/test/test_soring.c:218:
+ struct rte_soring *sor = NULL;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#327: FILE: app/test/test_soring.c:219:
+ struct rte_soring_param prm;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#344: FILE: app/test/test_soring.c:236:
+ set_soring_init_param(&prm, "enqueue/dequeue", sizeof(uint32_t *),
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#346: FILE: app/test/test_soring.c:238:
+ sz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#348: FILE: app/test/test_soring.c:240:
+ RTE_TEST_ASSERT_NOT_NULL(sor, "alloc failed for soring");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#349: FILE: app/test/test_soring.c:241:
+ rc = rte_soring_init(sor, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#350: FILE: app/test/test_soring.c:242:
+ RTE_TEST_ASSERT_SUCCESS(rc, "Failed to init soring");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#354: FILE: app/test/test_soring.c:246:
+ enqueued = rte_soring_enqueue_burst(sor, queue_objs_p, 5, &free_space);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#356: FILE: app/test/test_soring.c:248:
+ SORING_TEST_ASSERT(free_space, 5);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#357: FILE: app/test/test_soring.c:249:
+ SORING_TEST_ASSERT(enqueued, 5);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#360: FILE: app/test/test_soring.c:252:
+ enqueued = rte_soring_enqueue_bulk(sor, queue_objs_p, 7, &free_space);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#362: FILE: app/test/test_soring.c:254:
+ SORING_TEST_ASSERT(free_space, 5);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#363: FILE: app/test/test_soring.c:255:
+ SORING_TEST_ASSERT(enqueued, 0);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#366: FILE: app/test/test_soring.c:258:
+ enqueued = rte_soring_enqueue_burst(sor, queue_objs_p + 5, 7,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#368: FILE: app/test/test_soring.c:260:
+ SORING_TEST_ASSERT(free_space, 0);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#369: FILE: app/test/test_soring.c:261:
+ SORING_TEST_ASSERT(enqueued, 5);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#372: FILE: app/test/test_soring.c:264:
+ dequeued = rte_soring_dequeue_bulk(sor, dequeued_objs, 10, NULL);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#373: FILE: app/test/test_soring.c:265:
+ SORING_TEST_ASSERT(dequeued, 0);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#374: FILE: app/test/test_soring.c:266:
+ dequeued = rte_soring_dequeue_burst(sor, dequeued_objs, 10, NULL);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#375: FILE: app/test/test_soring.c:267:
+ SORING_TEST_ASSERT(dequeued, 0);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#380: FILE: app/test/test_soring.c:272:
+ dequeued = rte_soring_dequeue_bulk(sor, dequeued_objs, 10, NULL);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#381: FILE: app/test/test_soring.c:273:
+ SORING_TEST_ASSERT(dequeued, 0);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#382: FILE: app/test/test_soring.c:274:
+ dequeued = rte_soring_dequeue_burst(sor, dequeued_objs, 10, NULL);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#383: FILE: app/test/test_soring.c:275:
+ SORING_TEST_ASSERT(dequeued, 8);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#390: FILE: app/test/test_soring.c:282:
+ dequeued = rte_soring_dequeue_burst(sor, dequeued_objs, 1, NULL);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#391: FILE: app/test/test_soring.c:283:
+ SORING_TEST_ASSERT(dequeued, 0);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#394: FILE: app/test/test_soring.c:286:
+ dequeued = rte_soring_dequeue_burst(sor, dequeued_objs, 2, NULL);
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#395: FILE: app/test/test_soring.c:287:
+ SORING_TEST_ASSERT(dequeued, 2);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#402: FILE: app/test/test_soring.c:294:
+ rte_soring_dump(stdout, sor);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#408: FILE: app/test/test_soring.c:300:
+test_soring_acquire_release(void)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#411: FILE: app/test/test_soring.c:303:
+ struct rte_soring *sor = NULL;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#412: FILE: app/test/test_soring.c:304:
+ struct rte_soring_param prm;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#431: FILE: app/test/test_soring.c:323:
+ set_soring_init_param(&prm, "test_acquire_release", sizeof(uint32_t),
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#433: FILE: app/test/test_soring.c:325:
+ sz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#442: FILE: app/test/test_soring.c:334:
+ rc = rte_soring_init(sor, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#443: FILE: app/test/test_soring.c:335:
+ RTE_TEST_ASSERT_SUCCESS(rc, "failed to init soring");
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#446: FILE: app/test/test_soring.c:338:
+ enqueued = rte_soring_enqueux_burst(sor, queue_objs, rc_objs, 5,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#448: FILE: app/test/test_soring.c:340:
+ SORING_TEST_ASSERT(enqueued, 5);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#450: FILE: app/test/test_soring.c:342:
+ enqueued = rte_soring_enqueue_burst(sor, queue_objs + 5, 5,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#452: FILE: app/test/test_soring.c:344:
+ SORING_TEST_ASSERT(enqueued, 5);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#455: FILE: app/test/test_soring.c:347:
+ acquired = rte_soring_acquirx_burst(sor, acquired_objs,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#457: FILE: app/test/test_soring.c:349:
+ SORING_TEST_ASSERT(acquired, 5);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#466: FILE: app/test/test_soring.c:358:
+ rte_soring_release(sor, NULL, 0, 5, ftoken);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#469: FILE: app/test/test_soring.c:361:
+ acquired = rte_soring_acquirx_burst(sor, acquired_objs,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#471: FILE: app/test/test_soring.c:363:
+ SORING_TEST_ASSERT(acquired, 5);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#484: FILE: app/test/test_soring.c:376:
+ rte_soring_releasx(sor, NULL, rc_objs + 5, 0, 5,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#487: FILE: app/test/test_soring.c:379:
+ acquired = rte_soring_acquirx_burst(sor, acquired_objs,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#489: FILE: app/test/test_soring.c:381:
+ SORING_TEST_ASSERT(acquired, 10);
WARNING:TYPO_SPELLING: 'relase' may be misspelled - perhaps 'release'?
#491: FILE: app/test/test_soring.c:383:
+ /* ensure the associated rc's are the ones added at relase */
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#500: FILE: app/test/test_soring.c:392:
+ rte_soring_release(sor, NULL, 1, 10, ftoken);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#502: FILE: app/test/test_soring.c:394:
+ dequeued = rte_soring_dequeux_burst(sor, dequeued_objs, dequeued_rcs,
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#504: FILE: app/test/test_soring.c:396:
+ SORING_TEST_ASSERT(dequeued, 10);
WARNING:TYPO_SPELLING: 'relase' may be misspelled - perhaps 'release'?
#506: FILE: app/test/test_soring.c:398:
+ /* ensure the associated rc's are the ones added at relase */
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#514: FILE: app/test/test_soring.c:406:
+ rte_soring_dump(stdout, sor);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#520: FILE: app/test/test_soring.c:412:
+test_soring(void)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#524: FILE: app/test/test_soring.c:416:
+ if (test_soring_init() < 0)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#528: FILE: app/test/test_soring.c:420:
+ if (test_soring_get_memsize() < 0)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#532: FILE: app/test/test_soring.c:424:
+ if (test_soring_enqueue_dequeue() < 0)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#536: FILE: app/test/test_soring.c:428:
+ if (test_soring_acquire_release() < 0)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#540: FILE: app/test/test_soring.c:432:
+ if (test_soring_stages() < 0)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#549: FILE: app/test/test_soring.c:441:
+REGISTER_FAST_TEST(soring_autotest, true, true, test_soring);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#549: FILE: app/test/test_soring.c:441:
+REGISTER_FAST_TEST(soring_autotest, true, true, test_soring);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#561: FILE: app/test/test_soring_mt_stress.c:5:
+#include "test_soring_stress_impl.h"
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#564: FILE: app/test/test_soring_mt_stress.c:8:
+_st_ring_dequeue_burst(struct rte_soring *r, void **obj, uint32_t n,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#567: FILE: app/test/test_soring_mt_stress.c:11:
+ return rte_soring_dequeue_burst(r, obj, n, avail);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#571: FILE: app/test/test_soring_mt_stress.c:15:
+_st_ring_enqueue_bulk(struct rte_soring *r, void * const *obj, uint32_t n,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#574: FILE: app/test/test_soring_mt_stress.c:18:
+ return rte_soring_enqueue_bulk(r, obj, n, free);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#578: FILE: app/test/test_soring_mt_stress.c:22:
+_st_ring_acquire_burst(struct rte_soring *r, uint32_t stage, void **obj,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#581: FILE: app/test/test_soring_mt_stress.c:25:
+ return rte_soring_acquire_burst(r, obj, stage, num, token, avail);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#585: FILE: app/test/test_soring_mt_stress.c:29:
+_st_ring_release(struct rte_soring *r, uint32_t stage, uint32_t token,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#589: FILE: app/test/test_soring_mt_stress.c:33:
+ rte_soring_release(r, NULL, stage, num, token);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#592: FILE: app/test/test_soring_mt_stress.c:36:
+const struct test test_soring_mt_stress = {
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#607: FILE: app/test/test_soring_stress.c:5:
+#include "test_soring_stress.h"
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#642: FILE: app/test/test_soring_stress.c:40:
+ n += test_soring_mt_stress.nb_case;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#643: FILE: app/test/test_soring_stress.c:41:
+ k += run_test(&test_soring_mt_stress);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#650: FILE: app/test/test_soring_stress.c:48:
+REGISTER_TEST_COMMAND(soring_stress_autotest, test_ring_stress);
WARNING:TYPO_SPELLING: 'stdio' may be misspelled - perhaps 'studio'?
#666: FILE: app/test/test_soring_stress.h:10:
+#include <stdio.h>
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#669: FILE: app/test/test_soring_stress.h:13:
+#include <rte_soring.h>
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#691: FILE: app/test/test_soring_stress.h:35:
+extern const struct test test_soring_mt_stress;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#703: FILE: app/test/test_soring_stress_impl.h:6:
+#include "test_soring_stress.h"
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#706: FILE: app/test/test_soring_stress_impl.h:9:
+ * Stress test for soring enqueue/dequeue/acquire/release operations.
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#711: FILE: app/test/test_soring_stress_impl.h:14:
+ * Serves as both functional and performance test of soring
WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'?
#716: FILE: app/test/test_soring_stress_impl.h:19:
+#define RING_NAME "SORING_STRESS"
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#754: FILE: app/test/test_soring_stress_impl.h:57:
+ struct rte_soring *rng;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#767: FILE: app/test/test_soring_stress_impl.h:70:
+_st_ring_dequeue_burst(struct rte_soring *r, void **obj, uint32_t n,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#771: FILE: app/test/test_soring_stress_impl.h:74:
+_st_ring_enqueue_bulk(struct rte_soring *r, void * const *obj, uint32_t n,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#775: FILE: app/test/test_soring_stress_impl.h:78:
+_st_ring_acquire_burst(struct rte_soring *r, uint32_t stage, void **obj,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#779: FILE: app/test/test_soring_stress_impl.h:82:
+_st_ring_release(struct rte_soring *r, uint32_t stage, uint32_t token,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1132: FILE: app/test/test_soring_stress_impl.h:435:
+mt1_fini(struct rte_soring *rng, void *data)
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1139: FILE: app/test/test_soring_stress_impl.h:442:
+mt1_init(struct rte_soring **rng, void **data, uint32_t num,
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1146: FILE: app/test/test_soring_stress_impl.h:449:
+ struct rte_soring *r;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1149: FILE: app/test/test_soring_stress_impl.h:452:
+ struct rte_soring_param prm;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1164: FILE: app/test/test_soring_stress_impl.h:467:
+ /* alloc soring */
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1174: FILE: app/test/test_soring_stress_impl.h:477:
+ sz = rte_soring_get_memsize(&prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1184: FILE: app/test/test_soring_stress_impl.h:487:
+ rc = rte_soring_init(r, &prm);
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1186: FILE: app/test/test_soring_stress_impl.h:489:
+ printf("%s: rte_soring_init(r=%p,elems=%u,stages=%u) failed, "
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1215: FILE: app/test/test_soring_stress_impl.h:518:
+ struct rte_soring *r;
WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'?
#1267: FILE: app/test/test_soring_stress_impl.h:570:
+ rte_soring_dump(stdout, r);
WARNING:TYPO_SPELLING: 'enque' may be misspelled - perhaps 'enqueue'?
#1288: FILE: app/test/test_soring_stress_impl.h:591:
+ * - workers from 'even' group do deque+enque
total: 0 errors, 169 warnings, 1401 lines checked
Warning in app/test/test_soring_stress_impl.h:
Using __atomic_xxx/__ATOMIC_XXX built-ins, prefer rte_atomic_xxx/rte_memory_order_xxx
Warning in app/test/test_soring_stress.c:
Using REGISTER_TEST_COMMAND instead of REGISTER_<suite_name>_TEST
Please use __rte_cache_aligned only for struct or union types alignment.
next prev parent reply other threads:[~2024-09-17 12:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240917120946.1212-6-konstantin.v.ananyev@yandex.ru>
2024-09-17 11:44 ` |SUCCESS| pw144117-144121 " qemudev
2024-09-17 11:49 ` qemudev
2024-09-17 12:12 ` checkpatch [this message]
2024-09-17 13:04 ` |SUCCESS| pw144121 " 0-day Robot
2024-09-17 19:36 ` |SUCCESS| pw144117-144121 [PATCH] [v4,5/5] app/test: add unit tests dpdklab
2024-09-17 20:58 ` dpdklab
2024-09-17 21:18 ` dpdklab
2024-09-17 21:27 ` dpdklab
2024-09-17 22:03 ` dpdklab
2024-09-17 23:16 ` |PENDING| " dpdklab
2024-09-17 23:27 ` dpdklab
2024-09-17 23:30 ` |SUCCESS| " dpdklab
2024-09-17 23:52 ` |PENDING| " dpdklab
2024-09-17 23:57 ` dpdklab
2024-09-18 0:44 ` |SUCCESS| " dpdklab
2024-09-18 1:00 ` dpdklab
2024-09-18 1:14 ` |WARNING| " dpdklab
2024-09-18 2:47 ` |SUCCESS| " dpdklab
2024-09-18 4:11 ` dpdklab
2024-09-18 4:59 ` dpdklab
2024-09-18 5:21 ` dpdklab
2024-09-18 9:39 ` dpdklab
2024-09-22 8:16 ` dpdklab
2024-09-22 8:29 ` dpdklab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240917121213.81DDD121D10@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=konstantin.v.ananyev@yandex.ru \
--cc=test-report@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).