<div dir="ltr">Thanks Stephen.<div><br></div><div> While browsing the DPDK qos code, i figured out that existing PIPE-PROFILE cannot be updated or deleted at run time. </div><div>Was there any reason why this limitation ?</div><div><br></div><div>Thanks</div><div>Farooq.J</div></div><div dir="auto"></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 22 May, 2025, 20:51 Stephen Hemminger, <<a href="mailto:stephen@networkplumber.org" target="_blank">stephen@networkplumber.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, 22 May 2025 08:15:14 +0530<br>
farooq basha <<a href="mailto:farooq.juturu@gmail.com" rel="noreferrer" target="_blank">farooq.juturu@gmail.com</a>> wrote:<br>
<br>
> Thanks Stephen for addressing my queries , and it is helpful.<br>
> <br>
> One more follow up question on the same , Can DPDK HQOS be customized<br>
> based on Use case ?<br>
> <br>
> For example: Hqos config for one of the use cases , *One Port , One<br>
> Subport , 16 Pipes & Each Pipe with only one TC*.<br>
> 16 pipe config was allowed but changing the 13TCs<br>
> to 1TC is not allowed per Pipe.<br>
> <br>
> Can I still use 13 TCs but use the QueueSize as 0, Can that impact<br>
> performance ?<br>
> <br>
<br>
No. Current qos sched code has hard coded assumptions on number of pipes etc.<br>
I think it is modeled after some carrier standard and is not generally<br>
that useful.<br>
</blockquote></div>