From: Thomas Monjalon <thomas@monjalon.net>
To: Megha Ajmera <megha.ajmera@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org, jasvinder.singh@intel.com,
cristian.dumitrescu@intel.com, marcinx.danilewicz@intel.com,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH] sched: fix for tc_ov_enable flag position in subport structure.
Date: Mon, 06 Feb 2023 08:43:25 +0100 [thread overview]
Message-ID: <3205880.oiGErgHkdL@thomas> (raw)
In-Reply-To: <CAJFAV8wvViM=G7UhmAZ71AEQ4FDZUcmAE5zxcUVpJ_isVh532Q@mail.gmail.com>
10/01/2023 12:27, David Marchand:
> On Mon, Jan 9, 2023 at 3:59 PM Megha Ajmera <megha.ajmera@intel.com> wrote:
> >
> > Current position of "tv_ov_enable" variable in
>
> tc_ov_enabled*
>
>
> > rte_sched_subport structure makes the "memory" variable unused.
>
> I did not enter the beast... but my understanding is that some object
> internal to rte_sched_subport currently shares location with this
> tc_ov_enabled field.
> So please find a better title and describe the impact.
>
>
> >
> > Fixes: f5e60154ade ("sched: enable traffic class oversubscription conditionally")
> > CC: marcinx.danilewicz@intel.com
>
> This is stable@dpdk.org material, isn't it?
>
>
> > Signed-off-by: Megha Ajmera <megha.ajmera@intel.com>
Ping
Please update or the patch will be abandoned.
Jasvinder, Cristian, can you help?
next prev parent reply other threads:[~2023-02-06 7:43 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
2023-01-10 11:27 ` David Marchand
2023-02-06 7:43 ` Thomas Monjalon [this message]
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=3205880.oiGErgHkdL@thomas \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=david.marchand@redhat.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).