From: "Danilewicz, MarcinX" <marcinx.danilewicz@intel.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: "Ajmera, Megha" <megha.ajmera@intel.com>
Subject: RE: [PATCH v2] sched: enable CMAN at runtime
Date: Thu, 2 Jun 2022 09:57:51 +0000 [thread overview]
Message-ID: <PH0PR11MB578470F7A50D60223CD60DF98FDE9@PH0PR11MB5784.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM8PR11MB5670903A44E0DAE434C6E268EBDD9@DM8PR11MB5670.namprd11.prod.outlook.com>
+this time to dpdk.org , to test removal of automatic footer
Hi Cristian,
< snip >
> > +++ b/lib/sched/rte_sched.h
> > @@ -128,6 +128,8 @@ extern "C" {
> > enum rte_sched_cman_mode {
> > RTE_SCHED_CMAN_RED, /**< Random Early Detection (RED) */
> > RTE_SCHED_CMAN_PIE, /**< Proportional Integral Controller
< snip >
> Can you please explain why you need to add the new
> RTE_SCHED_CMAN_NONE value to this enumeration and what is the ABI
> breakage that you are trying to avoid?
>
well, it was third value for cases when no RED or PIE is configured from config file
Initially I have found this error:
1 data member change:
type of 'rte_sched_cman_params* rte_sched_subport_params::cman_params' changed:
in pointed to type 'struct rte_sched_cman_params' at rte_sched.h:166:1:
type size hasn't changed
1 data member change:
type of 'rte_sched_cman_mode rte_sched_cman_params::cman_mode' changed:
type size hasn't changed
1 enumerator insertion:
'rte_sched_cman_mode::RTE_SCHED_CMAN_NONE' value '0'
2 enumerator changes:
'rte_sched_cman_mode::RTE_SCHED_CMAN_RED' from value '0' to '1' at rte_sched.h:128:1
'rte_sched_cman_mode::RTE_SCHED_CMAN_PIE' from value '1' to '2' at rte_sched.h:128:1
Error: ABI issue reported for 'abidiff --suppr devtools/libabigail.abignore --no-added-syms
--headers-dir1 reference/usr/local/include --headers-dir2 install/usr/local/include reference
/dump/librte_sched.dump install/dump/librte_sched.dump'
ABIDIFF_ABI_CHANGE, this change requires a review (abidiff flagged this as a potential issue).
Then I moved RTE_SCHED_CMAN_NONE to the end of existing enum, as advices. That removed error above.
In that moment, I needed quick fix for discussion about change for showing approach. Not final fix.
< snip >
> The library expects the struct rte_sched_subport_params:: cman_params to
> be NULL when the CMAN is disabled, why is this not enough to detect that
> CMAN is disabled? I suggest to keep the current approach.
Ok, I'll try to use NULL instead.
Kind Regards,
/Marcin
next prev parent reply other threads:[~2022-06-02 9:58 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 13:53 [PATCH] " Marcin Danilewicz
2022-05-12 13:10 ` [PATCH v2] " Marcin Danilewicz
2022-05-30 11:19 ` Dumitrescu, Cristian
2022-05-30 14:03 ` Danilewicz, MarcinX
2022-06-02 9:57 ` Danilewicz, MarcinX [this message]
2022-05-30 11:35 ` Dumitrescu, Cristian
2022-06-07 10:40 ` Danilewicz, MarcinX
2022-06-08 9:42 ` [PATCH v3] " Marcin Danilewicz
2022-06-08 11:59 ` Dumitrescu, Cristian
2022-06-08 15:29 ` Danilewicz, MarcinX
2022-06-13 9:09 ` [PATCH v4] " Marcin Danilewicz
2022-06-17 11:48 ` Dumitrescu, Cristian
2022-06-20 13:56 ` [PATCH v5] ched: " Marcin Danilewicz
2022-06-20 14:49 ` Dumitrescu, Cristian
2022-06-21 8:20 ` Danilewicz, MarcinX
2022-06-21 8:16 ` [PATCH v6] sched: " Marcin Danilewicz
2022-06-21 13:27 ` Dumitrescu, Cristian
2022-06-22 15:12 ` Danilewicz, MarcinX
2022-07-04 9:19 ` [PATCH v7] " Marcin Danilewicz
2022-07-05 17:05 ` [PATCH v8] " Marcin Danilewicz
2022-07-05 18:00 ` Ajmera, Megha
2022-07-05 22:26 ` Danilewicz, MarcinX
2022-07-06 8:53 ` Singh, Jasvinder
2022-07-07 13:07 ` Danilewicz, MarcinX
2022-07-07 16:28 ` Singh, Jasvinder
2022-07-07 21:22 ` Danilewicz, MarcinX
2022-07-08 13:14 ` [PATCH v9] " Marcin Danilewicz
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=PH0PR11MB578470F7A50D60223CD60DF98FDE9@PH0PR11MB5784.namprd11.prod.outlook.com \
--to=marcinx.danilewicz@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=megha.ajmera@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).