Home
last modified time | relevance | path

Searched refs:LSC (Results 1 – 10 of 10) sorted by relevance

/f-stack/dpdk/drivers/net/mlx4/
H A Dmlx4_intr.c179 enum { LSC, RMV, }; in mlx4_interrupt_handler() enumerator
181 [LSC] = RTE_ETH_EVENT_INTR_LSC, in mlx4_interrupt_handler()
196 ++caught[LSC]; in mlx4_interrupt_handler()
/f-stack/dpdk/devtools/
H A Dwords-case.txt33 LSC
/f-stack/dpdk/doc/guides/nics/
H A Dfm10k.rst128 the switch goes down the DPDK app will receive a LSC event indicating link
130 the Rx/Tx queues. When switch comes up, a LSC event indicating ``LINK_UP`` is
H A Dena.rst141 * LSC event notification
/f-stack/dpdk/doc/guides/rel_notes/
H A Drelease_17_05.rst235 Implemented Rxq interrupt mode and LSC support for virtio-user as a virtual
240 * LSC interrupt for virtio-user + vhost-user as the backend.
368 * **LSC interrupt doesn't work for virtio-user + vhost-kernel.**
370 LSC interrupt cannot be detected when setting the backend, tap device,
H A Dknown_issues.rst702 Link Status Change(LSC) interrupt and packet receiving interrupt are all enabled in l3fwd-power
710 Use vfio-pci when LSC and packet receiving interrupt enabled.
H A Drelease_2_1.rst71 interrupts. When the RX interrupt and LSC interrupt are both enabled, only
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dlink_status_intr.rst167 … printf("Event type: %s\n", type == RTE_ETH_EVENT_INTR_LSC ? "LSC interrupt" : "unknown event");
/f-stack/dpdk/doc/guides/testpmd_app_ug/
H A Drun_app.rst400 Disable LSC interrupts for all ports, even those supporting it.
/f-stack/dpdk/doc/guides/prog_guide/
H A Denv_abstraction_layer.rst387 …nterrupt causes shares the same vector. In this case, when RX interrupt and LSC(link status change)