From: farooq basha <farooq.juturu@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Regarding HQOS with run-to-completion Model
Date: Tue, 27 May 2025 21:09:57 +0530 [thread overview]
Message-ID: <CA+xuiv0zZ82m9gUM5D73hLVC89si72piuax6jk_a6ZzHuoBzzg@mail.gmail.com> (raw)
In-Reply-To: <20250522082105.2aa03935@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Thanks Stephen.
While browsing the DPDK qos code, i figured out that existing
PIPE-PROFILE cannot be updated or deleted at run time.
Was there any reason why this limitation ?
Thanks
Farooq.J
On Thu, 22 May, 2025, 20:51 Stephen Hemminger, <stephen@networkplumber.org>
wrote:
> On Thu, 22 May 2025 08:15:14 +0530
> farooq basha <farooq.juturu@gmail.com> wrote:
>
> > Thanks Stephen for addressing my queries , and it is helpful.
> >
> > One more follow up question on the same , Can DPDK HQOS be
> customized
> > based on Use case ?
> >
> > For example: Hqos config for one of the use cases , *One Port , One
> > Subport , 16 Pipes & Each Pipe with only one TC*.
> > 16 pipe config was allowed but changing the
> 13TCs
> > to 1TC is not allowed per Pipe.
> >
> > Can I still use 13 TCs but use the QueueSize as 0, Can that impact
> > performance ?
> >
>
> No. Current qos sched code has hard coded assumptions on number of pipes
> etc.
> I think it is modeled after some carrier standard and is not generally
> that useful.
>
[-- Attachment #2: Type: text/html, Size: 1693 bytes --]
next prev parent reply other threads:[~2025-05-28 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 11:25 farooq basha
2025-05-21 14:18 ` Stephen Hemminger
2025-05-22 2:45 ` farooq basha
2025-05-22 15:21 ` Stephen Hemminger
2025-05-27 15:39 ` farooq basha [this message]
2025-05-27 15:44 ` Stephen Hemminger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+xuiv0zZ82m9gUM5D73hLVC89si72piuax6jk_a6ZzHuoBzzg@mail.gmail.com \
--to=farooq.juturu@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).