From: Megha Ajmera <megha.ajmera@intel.com>
To: dev@dpdk.org, jasvinder.singh@intel.com, cristian.dumitrescu@intel.com
Cc: stable@dpdk.org
Subject: [PATCH v2] sched: subport field is unused in hqos profile
Date: Wed, 5 Oct 2022 18:15:04 +0000 [thread overview]
Message-ID: <20221005181504.309060-1-megha.ajmera@intel.com> (raw)
In-Reply-To: <20220818061126.1454523-1-megha.ajmera@intel.com>
Removed ununsed subport field from profile.cfg
Correctly using subport profile id in subport config load.
Fixes: 802d214dc880 ("examples/qos_sched: update subport rate dynamically")
Cc: cristian.dumitrescu@intel.com
Signed-off-by: Megha Ajmera <megha.ajmera@intel.com>
---
examples/qos_sched/cfg_file.c | 2 +-
examples/qos_sched/profile.cfg | 2 --
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/examples/qos_sched/cfg_file.c b/examples/qos_sched/cfg_file.c
index 3d5d75fcf0..fa3e802363 100644
--- a/examples/qos_sched/cfg_file.c
+++ b/examples/qos_sched/cfg_file.c
@@ -157,7 +157,7 @@ cfg_load_subport_profile(struct rte_cfgfile *cfg,
profiles = rte_cfgfile_num_sections(cfg, "subport profile",
sizeof("subport profile") - 1);
- subport_params[0].n_pipe_profiles = profiles;
+ port_params.n_subport_profiles= profiles;
for (i = 0; i < profiles; i++) {
char sec_name[32];
diff --git a/examples/qos_sched/profile.cfg b/examples/qos_sched/profile.cfg
index c9ec187c93..e8de101b6c 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 prev parent reply other threads:[~2022-10-05 18:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 6:11 [PATCH] " Megha Ajmera
2022-10-05 18:15 ` Megha Ajmera [this message]
2022-10-05 18:24 ` [PATCH v3] " 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=20221005181504.309060-1-megha.ajmera@intel.com \
--to=megha.ajmera@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=stable@dpdk.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).