From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Ajmera, Megha" <megha.ajmera@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"marcinx.danilewicz@intel.com" <marcinx.danilewicz@intel.com>
Subject: RE: [PATCH] sched: fix for tc_ov_enable flag position in subport structure.
Date: Tue, 10 Jan 2023 11:12:07 +0000 [thread overview]
Message-ID: <CH0PR11MB5724D870E5762A0F6E9083AEEBFF9@CH0PR11MB5724.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230109145448.278463-1-megha.ajmera@intel.com>
> -----Original Message-----
> From: Ajmera, Megha <megha.ajmera@intel.com>
> Sent: Monday, January 9, 2023 2:55 PM
> To: dev@dpdk.org; Singh, Jasvinder <jasvinder.singh@intel.com>; Dumitrescu,
> Cristian <cristian.dumitrescu@intel.com>
> Cc: stable@dpdk.org; marcinx.danilewicz@intel.com
> Subject: [PATCH] sched: fix for tc_ov_enable flag position in subport structure.
>
> Current position of "tv_ov_enable" variable in
> rte_sched_subport structure makes the "memory" variable unused.
>
> Fixes: f5e60154ade ("sched: enable traffic class oversubscription conditionally")
> CC: marcinx.danilewicz@intel.com
> Signed-off-by: Megha Ajmera <megha.ajmera@intel.com>
> ---
> lib/sched/rte_sched.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/lib/sched/rte_sched.c b/lib/sched/rte_sched.c
> index c91697131d..eaecd7ceb4 100644
> --- a/lib/sched/rte_sched.c
> +++ b/lib/sched/rte_sched.c
> @@ -202,6 +202,9 @@ struct rte_sched_subport {
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2023-01-10 11:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 14:54 Megha Ajmera
2023-01-10 11:12 ` Dumitrescu, Cristian [this message]
2023-01-10 11:27 ` David Marchand
2023-02-06 7:43 ` Thomas Monjalon
2023-02-06 9:32 ` Dumitrescu, Cristian
2023-02-07 9:09 ` Ajmera, Megha
2023-02-07 6:10 ` [PATCH v2] sched: fix for incorrect alignment of bitmap, pipe and queue structs in subport Megha Ajmera
2023-02-19 22:40 ` Thomas Monjalon
2023-02-19 22:43 ` Thomas Monjalon
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=CH0PR11MB5724D870E5762A0F6E9083AEEBFF9@CH0PR11MB5724.namprd11.prod.outlook.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=marcinx.danilewicz@intel.com \
--cc=megha.ajmera@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).