| /dpdk/devtools/ |
| H A D | check-git-log.sh | 58 failure=false 127 \"$bad_line\": $bad_word --> $word\n" && failure=true;} 135 [ -z "$bad" ] || { printf "Headline too long:\n$bad\n" && failure=true;} 141 [ -z "$bad" ] || { printf "Line too long:\n$bad\n" && failure=true;} 149 && failure=true;} 156 [ -z "$bad" ] || { printf "Wrong tag:\n$bad\n" && failure=true;} 166 && failure=true;} 176 && failure=true;} 204 && failure=true;} 207 if $failure ; then [all …]
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | keep_alive.rst | 10 of this failure. Its purpose is to ensure the failure of the core 27 higher level fault management entity of the core failure in order to 32 to detect its failure.
|
| /dpdk/lib/eal/x86/include/ |
| H A D | rte_atomic_64.h | 192 int failure) in rte_atomic128_cmp_exchange() argument 196 RTE_SET_USED(failure); in rte_atomic128_cmp_exchange()
|
| /dpdk/lib/eal/arm/include/ |
| H A D | rte_atomic_64.h | 101 int failure) in rte_atomic128_cmp_exchange() argument 108 RTE_SET_USED(failure); in rte_atomic128_cmp_exchange()
|
| /dpdk/drivers/dma/ioat/ |
| H A D | ioat_dmadev.c | 78 ioat->failure = 0; in ioat_vchan_setup() 429 if (ioat->failure != 0) { in ioat_completed() 448 ioat->failure = ioat->regs->chanerr; in ioat_completed() 505 if (ioat->failure > 0) { in ioat_completed_status() 506 status[0] = __translate_status_ioat_to_dma(ioat->failure); in ioat_completed_status() 508 ioat->failure = 0; in ioat_completed_status()
|
| H A D | ioat_internal.h | 25 unsigned int failure; /* Used to store chanerr for error handling. */ member
|
| /dpdk/.github/workflows/ |
| H A D | build.yml | 149 - name: Upload logs on failure 150 if: failure() 289 - name: Upload logs on failure 290 if: failure()
|
| /dpdk/drivers/net/failsafe/ |
| H A D | failsafe_ops.c | 261 bool failure = true; in fs_rx_queue_stop() local 273 failure = false; in fs_rx_queue_stop() 279 return (failure) ? err : 0; in fs_rx_queue_stop() 314 bool failure = true; in fs_tx_queue_stop() local 326 failure = false; in fs_tx_queue_stop() 332 return (failure) ? err : 0; in fs_tx_queue_stop()
|
| /dpdk/doc/guides/contributing/ |
| H A D | unit_test.rst | 325 in order to reflect failure state back to the runner. 332 by returning a test result failure, using the ``TEST_FAILED`` error code. 341 but will also log details about the failure.
|
| /dpdk/config/ppc/ |
| H A D | meson.build | 13 # is used, resulting in a build failure.
|
| /dpdk/lib/eal/include/generic/ |
| H A D | rte_atomic.h | 1112 int failure);
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | la12xx.rst | 124 testcases to be skipped, but no failure should be reported.
|
| H A D | acc100.rst | 216 testcases to be skipped, but no failure should be reported.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | ip_fragment_reassembly_lib.rst | 60 … of reinserting existing keys into alternative locations, ip_frag_tbl_add() just returns a failure.
|
| H A D | rib_lib.rst | 131 In case of a next hop failure, we need to replace an active failed next hop with a
|
| H A D | link_bonding_poll_mode_drv_lib.rst | 62 thereby providing fault tolerance to slave failure. The single logical 176 - Validate flow for each slave, failure at least for one slave causes to 177 bond validation failure.
|
| H A D | graph_lib.rst | 378 On LPM lookup failure, objects are redirected to pkt_drop node.
|
| /dpdk/lib/hash/ |
| H A D | rte_cuckoo_hash.c | 1123 goto failure; in __rte_hash_add_key_with_hash() 1130 goto failure; in __rte_hash_add_key_with_hash() 1171 goto failure; in __rte_hash_add_key_with_hash() 1190 failure: in __rte_hash_add_key_with_hash()
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_16_04.rst | 336 * **i40e: Fixed failure of reading/writing RX control registers.** 340 failure. 437 * **examples/vhost: Fixed frequent mbuf allocation failure.**
|
| H A D | release_2_1.rst | 471 * **devargs: Fix crash on failure.** 916 * **mlx4: Fix possible crash on scattered mbuf allocation failure.**
|
| H A D | release_16_07.rst | 193 * **igb_uio: Fixed possible mmap failure for Linux >= 4.5.**
|
| H A D | release_18_02.rst | 17 to failure during initialization of secondary processes.
|
| /dpdk/doc/guides/nics/ |
| H A D | ena.rst | 152 * Device reset upon failure
|
| /dpdk/doc/guides/howto/ |
| H A D | debug_troubleshoot.rst | 364 * If the failure is on the enqueue stage for events, check if queue depth
|
| /dpdk/doc/guides/tools/ |
| H A D | testbbdev.rst | 231 rate matching is expected, or crc_fail when a CRC failure is expected.
|