Hi Elias,
You can find such solution in VPP 18.04 where VPP dpdk plugin is modified to
enable HQoS scheduler and shaping function which runs on a separate VPP thread
on TX path. The feature was deprecated in later releases. Hope that helps.
Thanks,
Jasvinder.
> -Original Message-
> F
May be packet fields (traffic from TRex) associated with pipe, tc, and queues
are not randomized, so traffic is only going to specific scheduler queues.
Please refer documentation to know offsets of packet fields.
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
hui12...@16
Hi Abeeha,
In the config file, hqos thread is allocated (cpu section), and hqos is’nt
enabled on interfaces (dpdk section). In the current state, hqos needs separate
thread (other than worker threads) for scheduling function, and also,
enablement on dpdk interfaces.
Thanks,
Jasvinder
From:
Hi Reza,
I tested HQoS on my fedora system as below and found it working, didn’t see any
issue;
1. Make build
2. Make run STARTUP_CONF=startup.conf
3. DGBvpp#
startup.conf
unix {
interactive
log /tmp/vpp.log
cli-listen /run/vpp/cli.sock
full-coredump
}
dpdk {
socket-mem 8
Hi Damjan,
I co-authored VPP HQoS work with Cristian. Thus, I volunteer myself to be the
maintainer.
Regards,
Jasvinder
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Damjan
Marion
Sent: Thursday, May 31, 2018 10:52 AM
To: vpp-dev
Subject: [vpp-dev] DPDK 18.05 is out
Fol
