| /dpdk/doc/guides/eventdevs/ |
| H A D | octeontx.rst | 26 - Supports ATOMIC, ORDERED, PARALLEL schedule types per flow 88 When eth_octeontx is used as Rx adapter event schedule type 104 When timvf is used as Event timer adapter event schedule type
|
| H A D | sw.rst | 55 schedule in a single schedule call performed by the service core. Note that
|
| H A D | cnxk.rst | 33 - Supports ATOMIC, ORDERED, PARALLEL schedule types per flow
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | eventdev.rst | 9 with features to schedule events. This is achieved using the PMD architecture 71 variables. For example the mbuf pointer in the union can used to schedule a 342 enqueue some events into the system for it to schedule. The events to be 454 The eventdev library allows an application to easily schedule events as it 457 the application with a generic method to schedule events. With the flexible
|
| H A D | traffic_management.rst | 65 level/position in the tree. The SP algorithm is used to schedule between 66 sibling nodes with different priority, while WFQ is used to schedule between 173 Priority (SP) and Weighted Fair Queuing (WFQ) algorithms to schedule input
|
| H A D | regexdev.rst | 162 identifier to specify the device queue pair to schedule the processing on.
|
| H A D | event_crypto_adapter.rst | 8 programming model with features to schedule events.
|
| H A D | qos_framework.rst | 432 The sequence of steps to schedule the next packet from the current pipe is: 507 …This means that scheduler is able to schedule NIC packets before the NIC actually needs those pack… 519 the scheduler should be able to schedule n packets faster than the same n packets are transmitted b…
|
| H A D | compressdev.rst | 615 identifier to specify the compression device queue pair to schedule the processing on.
|
| /dpdk/doc/guides/tools/ |
| H A D | testeventdev.rst | 85 P or p : Parallel schedule type 86 O or o : Ordered schedule type 87 A or a : Atomic schedule type 589 | | | nb_producers | At the last stage of the schedule list |
|
| /dpdk/drivers/net/hns3/ |
| H A D | hns3_intr.c | 2407 __atomic_store_n(&hw->reset.schedule, SCHEDULE_PENDING, in hns3_schedule_reset() 2416 if (__atomic_load_n(&hw->reset.schedule, __ATOMIC_RELAXED) == in hns3_schedule_reset() 2419 if (__atomic_load_n(&hw->reset.schedule, __ATOMIC_RELAXED) == in hns3_schedule_reset() 2423 __atomic_store_n(&hw->reset.schedule, SCHEDULE_REQUESTED, in hns3_schedule_reset() 2441 if (__atomic_load_n(&hw->reset.schedule, __ATOMIC_RELAXED) != in hns3_schedule_delayed_reset() 2444 __atomic_store_n(&hw->reset.schedule, SCHEDULE_DEFERRED, in hns3_schedule_delayed_reset()
|
| H A D | hns3_ethdev_vf.c | 2156 if (__atomic_load_n(&hw->reset.schedule, __ATOMIC_RELAXED) == in hns3vf_reset_service() 2158 __atomic_store_n(&hw->reset.schedule, SCHEDULE_REQUESTED, in hns3vf_reset_service() 2168 __atomic_store_n(&hw->reset.schedule, SCHEDULE_NONE, __ATOMIC_RELAXED); in hns3vf_reset_service() 2358 if (__atomic_load_n(&hw->reset.schedule, __ATOMIC_RELAXED) == in hns3vf_dev_init()
|
| H A D | hns3_ethdev.h | 401 uint16_t schedule; member
|
| H A D | hns3_ethdev.c | 5963 if (__atomic_load_n(&hw->reset.schedule, __ATOMIC_RELAXED) == in hns3_reset_service() 5965 __atomic_store_n(&hw->reset.schedule, SCHEDULE_REQUESTED, in hns3_reset_service() 5975 __atomic_store_n(&hw->reset.schedule, SCHEDULE_NONE, __ATOMIC_RELAXED); in hns3_reset_service() 6638 if (__atomic_load_n(&hw->reset.schedule, __ATOMIC_RELAXED) == in hns3_dev_init()
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | ipsec_secgw.rst | 147 --event-schedule-type TYPE 218 * ``--event-schedule-type TYPE``: queue schedule type, applies only when 223 When --event-schedule-type is set as RTE_SCHED_TYPE_ORDERED/ATOMIC, event 318 --event-schedule-type parallel --event-vector --vector-size 32 \ 336 * The ``--event-schedule-type`` option selects parallel ordering of event queues.
|
| H A D | l2_forward_event.rst | 72 * --eventq-sched=SCHED_MODE: Event queue schedule mode, Ordered, Atomic or Parallel. Atomic by de…
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | dpaa2_sec.rst | 193 By default, loose ordering is set for ordered schedule type event.
|
| /dpdk/.github/workflows/ |
| H A D | build.yml | 5 schedule:
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | fpga_5gnr_fec.rst | 183 configuration value should be set to 36:3. The schedule algorithm is based
|
| H A D | fpga_lte_fec.rst | 182 configuration value should be set to 36:3. The schedule algorithm is based
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_22_03.rst | 125 * Added support for ConnectX-7 capability to schedule traffic sending on timestamp.
|
| H A D | release_2_1.rst | 909 fixed schedule once every MLX4_PMD_TX_PER_COMP_REQ (currently 64) packets to
|
| H A D | release_18_05.rst | 224 The OcteonTx Timer block enables software to schedule events for a future
|
| /dpdk/doc/guides/contributing/ |
| H A D | patches.rst | 678 The schedule is updated in the `roadmap <https://core.dpdk.org/roadmap/#dates>`_.
|
| /dpdk/doc/guides/nics/ |
| H A D | mlx5.rst | 860 of granularity and engages the special test mode the check the schedule rate. 864 Starting with ConnectX-7 the capability to schedule traffic directly
|