From: Megha Ajmera <megha.ajmera@intel.com>
To: dev@dpdk.org, jasvinder.singh@intel.com, cristian.dumitrescu@intel.com
Subject: [PATCH] sched: subport field is unused in hqos profile
Date: Thu, 18 Aug 2022 06:11:26 +0000 [thread overview]
Message-ID: <20220818061126.1454523-1-megha.ajmera@intel.com> (raw)
Signed-off-by: Megha Ajmera <megha.ajmera@intel.com>
---
examples/qos_sched/profile.cfg | 2 --
1 file changed, 2 deletions(-)
diff --git a/examples/qos_sched/profile.cfg b/examples/qos_sched/profile.cfg
index d4b21c0170..8da5777538 100644
--- a/examples/qos_sched/profile.cfg
+++ b/examples/qos_sched/profile.cfg
@@ -26,8 +26,6 @@ number of subports per port = 1
number of pipes per subport = 4096
queue sizes = 64 64 64 64 64 64 64 64 64 64 64 64 64
-subport 0-8 = 0 ; These subports are configured with subport profile 0
-
[subport profile 0]
tb rate = 1250000000 ; Bytes per second
tb size = 1000000 ; Bytes
--
2.25.1
next reply other threads:[~2022-08-18 6:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 6:11 Megha Ajmera [this message]
2022-10-05 18:15 ` [PATCH v2] " Megha Ajmera
2022-10-05 18:24 ` [PATCH v3] " Megha Ajmera
-- strict thread matches above, loose matches on Subject: below --
2022-08-18 5:48 [PATCH] sched:subport " Megha Ajmera
2022-08-18 5:40 Megha Ajmera
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=20220818061126.1454523-1-megha.ajmera@intel.com \
--to=megha.ajmera@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.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).