From: Stephen Hemminger <stephen@networkplumber.org>
To: farooq basha <farooq.juturu@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Regarding HQOS with run-to-completion Model
Date: Tue, 27 May 2025 08:44:33 -0700 [thread overview]
Message-ID: <20250527084433.0233d470@hermes.local> (raw)
In-Reply-To: <CA+xuiv0zZ82m9gUM5D73hLVC89si72piuax6jk_a6ZzHuoBzzg@mail.gmail.com>
On Tue, 27 May 2025 21:09:57 +0530
farooq basha <farooq.juturu@gmail.com> wrote:
> 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 ?
My understanding was that the original author did this for a specific
carrier use case, and made restrictions to make it as fast as possible.
If you allowed updates, then locking would be necessary.
prev parent reply other threads:[~2025-05-27 15:44 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
2025-05-27 15:44 ` Stephen Hemminger [this message]
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=20250527084433.0233d470@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=farooq.juturu@gmail.com \
/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).