[neutron][qos][dpdk] is QoS supported with DPDK

Sean Mooney smooney at redhat.com
Tue Jan 15 21:05:06 UTC 2019

On Tue, 2019-01-15 at 19:44 +0000, cristian.calin at orange.com wrote:
> Hi all,
> Is QoS supported when DPDK is leveraged on the openvswitch?
max and max burst rates are supported i belive in both ingress and egress using
HTB in ovs-dpdk

there is no ovs-dpdk support for miniumium bandwidth qos at the dataplane level.
this is also true of kernel ovs. hardware offloaded ovs in thery could enforce minium bandwith gurarentees
if the nic supports it.

the minium bandwidth support in neutron based on placement reservations however should work with ovs-dpdk too
so once that is there while the datapane wont enforce the minium the scudler will prevent over subsriptions.

if you enforce a max bandwith policy equal to the min bandwith gurentee with a large burst rate
for all instnace on a host
you can fake a min bandwith gurrentee but its not quite the same thing as using a network backend the truely
supports it.

so yes max bandwith qos and dscp  policies work with ovs-dpkd and there may be support for min bandwith in stien/train


> From what I can tell the two are incompatible but I’m hoping someone has some information otherwise.
> Thanks,
> Cristian Calin
> ______________________________________________________________________________________________________________________
> ___
> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le
> signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles
> d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
> This message and its attachments may contain confidential or privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
> Thank you.

More information about the openstack-discuss mailing list