From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
"Ajmera, Megha" <megha.ajmera@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"marcinx.danilewicz@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, 6 Feb 2023 09:32:12 +0000 [thread overview]
Message-ID: <CH0PR11MB57244075FC133368EE2C06C3EBDA9@CH0PR11MB5724.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3205880.oiGErgHkdL@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Monday, February 6, 2023 7:43 AM
> To: Ajmera, Megha <megha.ajmera@intel.com>
> Cc: stable@dpdk.org; dev@dpdk.org; Singh, Jasvinder
> <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <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.
>
> 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?
>
>
>
Megha,
David asked for a better description of the fix and CC stable about a month ago, did you miss his email? These should be quick to handle, are you able to send V2?
Regards,
Cristian
next prev parent reply other threads:[~2023-02-06 9:32 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
2023-02-06 9:32 ` Dumitrescu, Cristian [this message]
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=CH0PR11MB57244075FC133368EE2C06C3EBDA9@CH0PR11MB5724.namprd11.prod.outlook.com \
--to=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 \
--cc=thomas@monjalon.net \
/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).