Home
last modified time | relevance | path

Searched refs:scheduler (Results 1 – 25 of 35) sorted by relevance

12

/dpdk/drivers/crypto/scheduler/
H A Drte_cryptodev_scheduler.c417 struct rte_cryptodev_scheduler *scheduler) { in rte_cryptodev_scheduler_load_user_scheduler() argument
439 if (strlen(scheduler->name) > RTE_CRYPTODEV_NAME_MAX_LEN - 1) { in rte_cryptodev_scheduler_load_user_scheduler()
441 "%u bytes.", scheduler->name, in rte_cryptodev_scheduler_load_user_scheduler()
447 if (strlen(scheduler->description) > in rte_cryptodev_scheduler_load_user_scheduler()
450 "%u bytes.", scheduler->description, in rte_cryptodev_scheduler_load_user_scheduler()
454 strlcpy(sched_ctx->description, scheduler->description, in rte_cryptodev_scheduler_load_user_scheduler()
462 sched_ctx->ops.worker_attach = scheduler->ops->worker_attach; in rte_cryptodev_scheduler_load_user_scheduler()
463 sched_ctx->ops.worker_detach = scheduler->ops->worker_detach; in rte_cryptodev_scheduler_load_user_scheduler()
464 sched_ctx->ops.option_set = scheduler->ops->option_set; in rte_cryptodev_scheduler_load_user_scheduler()
465 sched_ctx->ops.option_get = scheduler->ops->option_get; in rte_cryptodev_scheduler_load_user_scheduler()
[all …]
H A Dscheduler_roundrobin.c205 static struct rte_cryptodev_scheduler scheduler = { variable
213 struct rte_cryptodev_scheduler *crypto_scheduler_roundrobin = &scheduler;
H A Drte_cryptodev_scheduler.h102 struct rte_cryptodev_scheduler *scheduler);
/dpdk/doc/guides/nics/
H A Dsoftnic.rst73 #. ``tm_n_queues``: number of traffic manager's scheduler queues. The traffic manager
76 #. ``tm_qsize0``: size of scheduler queue 0 (traffic class 0) of the pipes/subscribers.
79 #. ``tm_qsize1``: size of scheduler queue 1 (traffic class 1) of the pipes/subscribers.
82 #. ``tm_qsize2``: size of scheduler queue 2 (traffic class 2) of the pipes/subscribers.
85 #. ``tm_qsize3``: size of scheduler queue 3 (traffic class 3) of the pipes/subscribers.
88 #. ``tm_qsize4``: size of scheduler queue 4 (traffic class 4) of the pipes/subscribers.
91 #. ``tm_qsize5``: size of scheduler queue 5 (traffic class 5) of the pipes/subscribers.
94 #. ``tm_qsize6``: size of scheduler queue 6 (traffic class 6) of the pipes/subscribers.
97 #. ``tm_qsize7``: size of scheduler queue 7 (traffic class 7) of the pipes/subscribers.
100 #. ``tm_qsize8``: size of scheduler queue 8 (traffic class 8) of the pipes/subscribers.
[all …]
/dpdk/doc/guides/cryptodevs/
H A Dscheduler.rst11 .. figure:: img/scheduler-overview.*
58 attached to the scheduler using this parameter, simply filling the name
83 * The scheduler cryptodev cannot be started unless the scheduling mode
85 scheduler in the run-time, like attach/detach worker(s), change
87 the scheduler first, otherwise an error will be returned.
144 secondary worker. In this mode, the scheduler will enqueue the incoming
155 round-robin manner. If scheduler cannot enqueue entire burst to the same worker,
160 For large packets (1.5 kbytes) scheduler shows linear scaling in performance
H A Dindex.rst30 scheduler
/dpdk/doc/guides/sample_app_ug/
H A Dl2_forward_event.rst107 To run application with S/W scheduler, it uses following DPDK services:
109 * Software scheduler
115 scheduler. Following is the sample command:
258 Application can use either H/W or S/W based event device scheduler
268 In case of S/W scheduler, application runs eventdev scheduler service on service
270 run S/W scheduler.
274 :start-after: Running eventdev scheduler service on service core. 8<
290 In case of S/W scheduler, an extra event queue is created which will be used for
307 In case of S/W scheduler, an extra event port is created by DPDK library which
329 For S/W scheduler instead of dedicated adapters, common Rx/Tx adapters are
[all …]
H A Dqos_scheduler.rst12 The architecture of the QoS scheduler application is shown in the following figure.
26 The worker thread dequeues the packets from the ring and calls the QoS scheduler enqueue/dequeue fu…
122 needed for the QoS scheduler configuration.
143 went through the scheduler properly and the number of packets that were dropped.
148 went through the scheduler properly and the number of packets that were dropped.
188 …ow configurations using different ports but sharing the same core for QoS scheduler is given below:
H A Dl3_forward.rst22 Eventdev can optionally use S/W or H/W (if supported by platform) scheduler
195 If application uses S/W scheduler, it uses following DPDK services:
197 * Software scheduler
203 scheduler. Following is the sample command:
H A Deventdev_pipeline.rst40 * ``-e4``: core mask 0x4 for the software scheduler
/dpdk/doc/guides/prog_guide/
H A Dqos_framework.rst251 /* Hierarchical scheduler enqueue */
255 /* Hierarchical scheduler dequeue */
379 keeps the scheduler data structures internal to the same core.
473 the port scheduler is woken up (interrupt based or polling based,
482 Every time the scheduler decides to send a packet out to the NIC TX for transmission, the scheduler…
495 The scheduler reads the current time on every dequeue invocation.
502 The scheduler maintains an internal time reference of the NIC time.
516 The scheduler round trip delay (SRTD) is the time (number of CPU cycles) between two consecutive ex…
1136 the lower the performance of the scheduler is.
1380 For much smaller scheduler hierarchies,
[all …]
H A Deventdev.rst16 scheduler that selects packets for them based on programmer-specified criteria.
138 core, but the scheduler must ensure that on egress the packets are returned to
193 For example, to create an instance of the software eventdev scheduler, the
/dpdk/doc/guides/eventdevs/
H A Dsw.rst93 The scheduler minimum number of events that are processed can be increased to
98 moved to the next stage in the scheduler. Default value is 1.
100 * ``refill_once`` is a switch that when set instructs the scheduler to deque
139 The software eventdev is a centralized scheduler, requiring a service core to
H A Ddpaa.rst19 - Hardware based event scheduler
H A Ddpaa2.rst20 - Hardware based event scheduler
H A Docteontx.rst21 - HW event scheduler
H A Dcnxk.rst28 - HW event scheduler
/dpdk/examples/eventdev_pipeline/
H A Dpipeline_worker_generic.c23 if (fdata->cap.scheduler) in worker_generic()
24 fdata->cap.scheduler(lcore_id); in worker_generic()
78 if (fdata->cap.scheduler) in worker_generic_burst()
79 fdata->cap.scheduler(lcore_id); in worker_generic_burst()
572 caps->scheduler = schedule_devices; in set_worker_generic_setup_data()
H A Dpipeline_common.h40 schedule_loop scheduler; member
H A Dpipeline_worker_tx.c888 fdata->cap.scheduler = NULL; in init_adapters()
1009 caps->scheduler = schedule_devices; in set_worker_tx_enq_setup_data()
/dpdk/drivers/crypto/
H A Dmeson.build20 'scheduler',
/dpdk/doc/guides/linux_gsg/
H A Denable_func.rst93 it is possible for the Linux scheduler to run other tasks on those cores also.
95 …le to use the ``isolcpus`` Linux kernel parameter to isolate them from the general Linux scheduler.
/dpdk/doc/api/
H A Ddoxy-api.conf.in9 @TOPDIR@/drivers/crypto/scheduler \
H A Ddoxy-api-index.md131 [scheduler] (@ref rte_sched.h),
/dpdk/examples/qos_sched/
H A Dprofile.cfg4 ; This file enables the following hierarchical scheduler configuration for each

12