* [dpdk-dev] Regarding HQOS with run-to-completion Model
@ 2025-04-28 11:25 farooq basha
0 siblings, 0 replies; only message in thread
From: farooq basha @ 2025-04-28 11:25 UTC (permalink / raw)
To: dev
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
Hello DevTeam,
I am planning to use DPDK HQOS for Traffic shaping with a
run-to-completion Model. While I was reading the dpdk-qos document, I came
across the following statement.
"*Running enqueue and dequeue operations for the same output port from
different cores is likely to cause significant impact on scheduler’s
performance and it is therefore not recommended"*
Let's take an example, Port1 & Port2 have 4 Rx queues and each Queue
mapped to a different CPU. Traffic coming on port1 gets forwarded to port2
. With the above limitation application needs to take a lock before doing
rte_sched_port_enqueue & dequeue operation. Performance is limited to only
1 CPU even though Traffic is coming on 4 Different CPUs.
Correct me if my understanding is Wrong?
Thanks
Basha
[-- Attachment #2: Type: text/html, Size: 2727 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2025-05-05 12:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-04-28 11:25 [dpdk-dev] Regarding HQOS with run-to-completion Model farooq basha
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).