Home
last modified time | relevance | path

Searched refs:callbacks (Results 1 – 25 of 53) sorted by relevance

123

/dpdk/lib/telemetry/
H A Dtelemetry_legacy.c61 if (num_legacy_callbacks >= (int) RTE_DIM(callbacks)) in rte_telemetry_legacy_register()
66 snprintf(callbacks[num_legacy_callbacks].cmd, MAX_LEN, in rte_telemetry_legacy_register()
68 snprintf(callbacks[num_legacy_callbacks].data, MAX_LEN, in rte_telemetry_legacy_register()
71 callbacks[num_legacy_callbacks].fn = fn; in rte_telemetry_legacy_register()
194 char *action_ptr = strstr(buffer, callbacks[i].action); in parse_client_request()
195 char *cmd_ptr = strstr(buffer, callbacks[i].cmd); in parse_client_request()
196 char *data_ptr = strstr(buffer, callbacks[i].data); in parse_client_request()
200 char action_sep = action_ptr[strlen(callbacks[i].action)]; in parse_client_request()
201 char cmd_sep = cmd_ptr[strlen(callbacks[i].cmd)]; in parse_client_request()
208 data_sep = data_ptr[strlen(callbacks[i].data)]; in parse_client_request()
[all …]
H A Dtelemetry.c61 static struct cmd_callback *callbacks; variable
80 new_callbacks = realloc(callbacks, sizeof(callbacks[0]) * (num_callbacks + 1)); in rte_telemetry_register_cmd()
85 callbacks = new_callbacks; in rte_telemetry_register_cmd()
91 memmove(callbacks + i + 1, callbacks + i, in rte_telemetry_register_cmd()
94 strlcpy(callbacks[i].cmd, cmd, MAX_CMD_LEN); in rte_telemetry_register_cmd()
95 callbacks[i].fn = fn; in rte_telemetry_register_cmd()
114 rte_tel_data_add_array_string(d, callbacks[i].cmd); in list_commands()
141 if (strcmp(params, callbacks[i].cmd) == 0) { in command_help()
143 callbacks[i].help); in command_help()
377 if (strcmp(cmd, callbacks[i].cmd) == 0) { in client_handler()
[all …]
/dpdk/lib/eal/freebsd/
H A Deal_interrupts.c117 !TAILQ_EMPTY(&src->callbacks)) { in rte_intr_callback_register()
147 TAILQ_INIT(&src->callbacks); in rte_intr_callback_register()
153 if (TAILQ_EMPTY(&src->callbacks)) in rte_intr_callback_register()
156 TAILQ_INSERT_TAIL(&(src->callbacks), callback, next); in rte_intr_callback_register()
202 TAILQ_REMOVE(&(src->callbacks), callback, next); in rte_intr_callback_register()
203 if (TAILQ_EMPTY(&(src->callbacks))) { in rte_intr_callback_register()
337 TAILQ_REMOVE(&src->callbacks, cb, next); in rte_intr_callback_unregister()
344 if (TAILQ_EMPTY(&src->callbacks)) { in rte_intr_callback_unregister()
532 TAILQ_FOREACH(cb, &src->callbacks, next) { in eal_intr_process_interrupts()
577 TAILQ_REMOVE(&src->callbacks, cb, next); in eal_intr_process_interrupts()
[all …]
/dpdk/lib/gpudev/
H A Dgpudev.c229 TAILQ_INIT(&dev->callbacks); in rte_gpu_allocate()
277 TAILQ_INIT(&dev->callbacks); in rte_gpu_attach()
379 struct rte_gpu_callback_list *callbacks; in rte_gpu_callback_register() local
402 callbacks = &gpus[next_dev].callbacks; in rte_gpu_callback_register()
405 TAILQ_FOREACH(callback, callbacks, next) { in rte_gpu_callback_register()
435 struct rte_gpu_callback_list *callbacks; in rte_gpu_callback_unregister() local
458 callbacks = &gpus[next_dev].callbacks; in rte_gpu_callback_unregister()
465 TAILQ_REMOVE(callbacks, callback, next); in rte_gpu_callback_unregister()
477 struct rte_gpu_callback_list *callbacks; in gpu_free_callbacks() local
480 callbacks = &dev->callbacks; in gpu_free_callbacks()
[all …]
H A Dgpudev_driver.h78 TAILQ_HEAD(rte_gpu_callback_list, rte_gpu_callback) callbacks;
/dpdk/doc/guides/sample_app_ug/
H A Drxtx_callbacks.rst8 demonstrates the use of user defined callbacks on received and transmitted
9 packets. The application performs a simple latency check, using callbacks, to
66 callbacks are added. This is explained in the next section:
81 The RX and TX callbacks are added to the ports/queues as function pointers:
85 :start-after: RX and TX callbacks are added to the ports. 8<
86 :end-before: >8 End of RX and TX callbacks.
H A Dintro.rst73 * :doc:`RX/TX callbacks Application<rxtx_callbacks>`: The RX/TX
74 callbacks sample application is a packet forwarding application that
75 demonstrates the use of user defined callbacks on received and transmitted
77 (packet arrival) and TX (packet transmission) by adding callbacks to the RX
H A Dlink_status_intr.rst25 …lication can be used to demonstrate the usage of link status interrupt and its user space callbacks
117 when a link status change is present and calls the user space callbacks registered by the applicati…
124 The application can register one or more callbacks to a specific port and interrupt event.
130 :end-before: >8 End of registering one or more callbacks.
/dpdk/lib/eal/linux/
H A Deal_interrupts.c516 if (TAILQ_EMPTY(&src->callbacks)) in rte_intr_callback_register()
543 TAILQ_INIT(&src->callbacks); in rte_intr_callback_register()
544 TAILQ_INSERT_TAIL(&(src->callbacks), callback, in rte_intr_callback_register()
658 TAILQ_REMOVE(&src->callbacks, cb, next); in rte_intr_callback_unregister()
665 if (TAILQ_EMPTY(&src->callbacks)) { in rte_intr_callback_unregister()
988 for (cb = TAILQ_FIRST(&src->callbacks); cb; in eal_intr_process_interrupts()
991 TAILQ_REMOVE(&src->callbacks, cb, next); in eal_intr_process_interrupts()
1010 TAILQ_FOREACH(cb, &src->callbacks, next) { in eal_intr_process_interrupts()
1032 TAILQ_REMOVE(&src->callbacks, cb, next); in eal_intr_process_interrupts()
1041 if (TAILQ_EMPTY(&src->callbacks)) { in eal_intr_process_interrupts()
[all …]
/dpdk/doc/guides/nics/
H A Dvirtio.rst211 Virtio driver has 6 Rx callbacks and 3 Tx callbacks.
213 Rx callbacks:
238 Tx callbacks:
249 By default, the non-vector callbacks are used:
259 Vector callbacks will be used when:
263 The corresponding callbacks are:
267 There is no vector callbacks for packed virtqueue for now.
275 In-order callbacks only work on simulated virtio user vdev.
497 Rx/Tx callbacks of each Virtio path
501 be selected automatically. Rx callbacks and Tx callbacks for each virtio path
[all …]
/dpdk/drivers/net/sfc/
H A Dsfc_ev.c578 efx_ev_qpoll(evq->common, &evq->read_ptr, evq->callbacks, evq); in sfc_ev_qpoll()
702 evq->callbacks = &sfc_ev_callbacks_efx_rx; in sfc_ev_qstart()
704 evq->callbacks = &sfc_ev_callbacks_dp_rx; in sfc_ev_qstart()
708 evq->callbacks = &sfc_ev_callbacks_efx_tx; in sfc_ev_qstart()
710 evq->callbacks = &sfc_ev_callbacks_dp_tx; in sfc_ev_qstart()
712 evq->callbacks = &sfc_ev_callbacks; in sfc_ev_qstart()
721 efx_ev_qcreate_check_init_done(evq->common, evq->callbacks, evq); in sfc_ev_qstart()
774 evq->callbacks = NULL; in sfc_ev_qstop()
H A Dsfc_ev.h47 const efx_ev_callbacks_t *callbacks; member
/dpdk/examples/fips_validation/
H A Dfips_validation.c408 for (j = 0; info.callbacks[j].key != NULL; j++) in fips_test_parse_one_case()
409 if (strstr(info.vec[i], info.callbacks[j].key)) { in fips_test_parse_one_case()
410 ret = info.callbacks[j].cb( in fips_test_parse_one_case()
411 info.callbacks[j].key, in fips_test_parse_one_case()
412 info.vec[i], info.callbacks[j].val); in fips_test_parse_one_case()
H A Dfips_validation_gcm.c205 info.callbacks = gcm_enc_vectors; in parse_test_gcm_init()
210 info.callbacks = gcm_dec_vectors; in parse_test_gcm_init()
H A Dfips_validation_hmac.c99 info.callbacks = hmac_tests_vectors; in parse_test_hmac_init()
H A Dfips_validation_cmac.c113 info.callbacks = cmac_tests_vectors; in parse_test_cmac_init()
H A Dfips_validation_sha.c105 info.callbacks = sha_tests_vectors; in parse_test_sha_init()
H A Dfips_validation_xts.c113 info.callbacks = xts_tests_vectors; in parse_test_xts_init()
H A Dfips_validation_aes.c183 info.callbacks = aes_tests_vectors; in parse_test_aes_init()
/dpdk/doc/guides/cryptodevs/
H A Dvirtio.rst40 Rx callbacks:
44 Tx callbacks:
/dpdk/doc/guides/rel_notes/
H A Drelease_1_8.rst14 * Support for registration of link status change callbacks with link bonding devices.
/dpdk/doc/guides/prog_guide/
H A Dkernel_nic_interface.rst192 User callbacks are executed while kernel module holds the ``rtnl`` lock, this
193 causes a deadlock when callbacks run control commands on another Linux kernel
207 support callbacks that requires rtnl lock to work (interface down).
265 There are currently four callbacks for which the user can register
308 In order to run these callbacks, the application must periodically call
312 tasks. Typically DPDK applications which use these callbacks will need
H A Dpdump_lib.rst66 and enables the packet capture by registering the Ethernet RX and TX callbacks for the given port o…
82 disables the packet capture by removing the Ethernet RX and TX callbacks for the given port or devi…
H A Dthread_safety_dpdk_functions.rst72 callbacks may be called in an additional thread outside the main DPDK processing threads.
73 These function callbacks should avoid manipulating DPDK objects that are also managed by the normal…
H A Dmulti_proc_support.rst223 These callbacks will be called from within a dedicated IPC or interrupt thread
330 it safe to allocate/free memory inside IPC callbacks. Attempting to do so may
333 Asynchronous request callbacks may be triggered either from IPC thread or from
336 inside asynchronous IPC request callbacks. This limitation does not apply to
339 If callbacks spend a long time processing the incoming requests, the requestor
349 This is important when registering callbacks during DPDK initialization.

123