Searched refs:notify (Results 1 – 18 of 18) sorted by relevance
| /dpdk/drivers/net/enic/base/ |
| H A D | vnic_dev.c | 43 struct vnic_devcmd_notify *notify; member 961 vdev->notify = notify_addr; in vnic_dev_notify_setcmd() 983 if (vdev->notify || vdev->notify_pa) { in vnic_dev_notify_set() 984 return vnic_dev_notify_setcmd(vdev, vdev->notify, in vnic_dev_notify_set() 1012 vdev->notify = NULL; in vnic_dev_notify_unsetcmd() 1022 if (vdev->notify && !vnic_dev_in_reset(vdev)) { in vnic_dev_notify_unset() 1025 vdev->notify, in vnic_dev_notify_unset() 1039 if (!vdev->notify || !vdev->notify_sz) in vnic_dev_notify_ready() 1044 rte_memcpy(&vdev->notify_copy, vdev->notify, vdev->notify_sz); in vnic_dev_notify_ready() 1149 if (vdev->notify) in vnic_dev_unregister() [all …]
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | keep_alive.rst | 9 to detect 'failed' DPDK cores and notify a fault management entity 26 A real life application might use this callback function to notify a
|
| H A D | vhost_crypto.rst | 54 guest works in polling mode, thus will NOT notify the guest completion of
|
| /dpdk/doc/guides/vdpadevs/ |
| H A D | mlx5.rst | 73 and interrupts are configured to the device in order to notify traffic for the
|
| H A D | ifc.rst | 44 route HW interrupt to virtio driver, create notify relay thread to translate
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | ntb.rst | 14 Also, the PMD allows to use doorbell registers to notify the peer and share
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | event_ethernet_tx_adapter.rst | 121 The application needs to notify the adapter about the transmit port and queue used
|
| H A D | vhost_lib.rst | 423 Called to get the notify area info of the queue.
|
| H A D | poll_mode_drv.rst | 608 For example when PF is reset, the PF sends a message to notify VFs of
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | deprecation.rst | 120 in order to notify errors instead of calling ``rte_exit``.
|
| H A D | release_20_02.rst | 84 * Added PF support Malicious Device Drive event catch and notify.
|
| H A D | release_16_07.rst | 44 mailbox message to notify each VF. To handle this link up/down event,
|
| H A D | release_19_11.rst | 70 * PMDs notify the validity of ``rte_mbuf::hash:rss`` to the application
|
| /dpdk/doc/guides/howto/ |
| H A D | vfd.rst | 304 Normally if a VF received this notification, the driver should notify the
|
| /dpdk/doc/guides/nics/ |
| H A D | i40e.rst | 46 - Malicious Device Drive event catch and notify 630 interface for VF to request the RX descriptor mode, also no interface to notify
|
| H A D | bnxt.rst | 338 * RX: check and remove CRC, notify the application on CRC error 530 // notify application VLAN strip via mbuf
|
| H A D | virtio.rst | 37 vring, make them available to the device, and then notify the host back
|
| /dpdk/drivers/net/bnx2x/ |
| H A D | elink.c | 932 struct elink_vars *vars, uint8_t notify); 14820 uint8_t notify) in elink_analyze_link_error() argument 14882 if (notify) in elink_analyze_link_error() 14900 uint8_t notify) in elink_check_half_open_conn() argument 14930 LINK_STATUS_NONE, notify); in elink_check_half_open_conn() 14949 LINK_STATUS_NONE, notify); in elink_check_half_open_conn()
|