From: "Singh, Jasvinder" <jasvinder.singh@intel.com>
To: "Danilewicz, MarcinX" <marcinx.danilewicz@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "Ajmera, Megha" <megha.ajmera@intel.com>
Subject: RE: [PATCH v11] sched: enable CMAN at runtime
Date: Tue, 26 Jul 2022 13:49:02 +0000 [thread overview]
Message-ID: <CY4PR11MB158958D22554EE5FA5F99AC2E0949@CY4PR11MB1589.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220715145110.592908-1-marcinx.danilewicz@intel.com>
> -----Original Message-----
> From: Danilewicz, MarcinX <marcinx.danilewicz@intel.com>
> Sent: Friday, July 15, 2022 3:51 PM
> To: dev@dpdk.org; Singh, Jasvinder <jasvinder.singh@intel.com>;
> Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: Ajmera, Megha <megha.ajmera@intel.com>
> Subject: [PATCH v11] sched: enable CMAN at runtime
>
> Added changes to enable CMAN (RED or PIE) at init from profile configuration
> file.
>
> By default CMAN code is enable but not in use, when there is no RED or PIE
> profile configured.
>
> Signed-off-by: Marcin Danilewicz <marcinx.danilewicz@intel.com>
> ---
> Log: v2 change in rte_sched.h to avoid ABI breakage.
> v3 changes from comments
> v4 rebase to 22.07-rc1
> v5 rebase to main latest
> v6 commit message fixed
> v7 changes from comments
> v8 with changes from comments
> v9 changes from comments
> tmgr.c
> cman_params set to null
> qos_sched/cfg_file.c
> removed redundant cman_params to NULL assignement
> subport_params[].cman_params assigned
> only when CMAN enabled
> v10 removed ip_pipeline app build error from change
> in tmgr.c
> v11 added cman_enabled flag instead
> of testing cman_params.cman_mode variable
> ---
Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
next prev parent reply other threads:[~2022-07-26 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220708131431.148279-1-marcinx.danilewicz>
2022-07-08 14:22 ` [PATCH v10] " Marcin Danilewicz
2022-07-15 14:51 ` [PATCH v11] " Marcin Danilewicz
2022-07-26 13:49 ` Singh, Jasvinder [this message]
2022-07-27 11:58 ` Danilewicz, MarcinX
2022-08-25 14:09 ` 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=CY4PR11MB158958D22554EE5FA5F99AC2E0949@CY4PR11MB1589.namprd11.prod.outlook.com \
--to=jasvinder.singh@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=marcinx.danilewicz@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).