This raises general question about DPDK HQOS in VPP, I don't think we have anybody on this list who can help with question like this one. Should be better to take it out than to keep something unmaintained, incomplete and untested?
-- Damjan > On 1 May 2018, at 15:32, Reza Mirzaei <mirzaei.r...@ut.ac.ir> wrote: > > Hi > > I want to set up quality of service in vpp according to these commands > <https://docs.fd.io/vpp/18.07/clicmd_src_plugins_dpdk_device.html>, but i > don't understand how can i distinguish between different customers from an > interface?? because it said here > <https://docs.fd.io/vpp/18.07/clicmd_src_plugins_dpdk_device.html#clicmd_set_dpdk_interface_hqos_pipe> > that currently there is not an API to create a new HQoS pipe profile and > just one is created by default in the code, also it said here > <https://docs.fd.io/vpp/18.07/clicmd_src_plugins_dpdk_device.html#clicmd_set_dpdk_interface_hqos_pktfield> > that currently only one subport is supported, so it can be concluded that > only one pipe profile type could be created for an interface and we just can > distinguish between interfaces. > > I want to be able to set different parameters (e.g. token_bucket_rate) for > different pipes on the same interface. > > can you please help me in this matter? > > Best regards > > Reza > >
