From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Ajmera, Megha" <megha.ajmera@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>,
"Thakur, Sham Singh" <sham.singh.thakur@intel.com>
Subject: RE: [PATCH] Revert "sched: enable traffic class oversubscription unconditionally"
Date: Mon, 14 Mar 2022 10:47:06 +0000 [thread overview]
Message-ID: <DM8PR11MB567083D84D0073B9558A6336EB0F9@DM8PR11MB5670.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220314095916.53574-1-megha.ajmera@intel.com>
> -----Original Message-----
> From: Ajmera, Megha <megha.ajmera@intel.com>
> Sent: Monday, March 14, 2022 9:59 AM
> To: dev@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; Singh,
> Jasvinder <jasvinder.singh@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>; Thakur, Sham Singh
> <sham.singh.thakur@intel.com>
> Subject: [PATCH] Revert "sched: enable traffic class oversubscription
> unconditionally"
>
> This reverts commit d91c4b1bb5a938734fe8e66da8f965304919f38e.
>
> When enabling TC OV unconditionally, it is observed the performance
> drops by ~20% hence reverting this commit.
>
> Signed-off-by: Megha Ajmera <megha.ajmera@intel.com>
> ---
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
We are reworking the original patch into a run-time configurable option and will resend the improved version shortly during the 22.07 development cycle.
prev parent reply other threads:[~2022-03-14 10:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 9:59 Megha Ajmera
2022-03-14 10:32 ` Kevin Traynor
2022-03-14 12:27 ` [PATCH v2] " Megha Ajmera
2022-03-15 11:22 ` Thomas Monjalon
2022-03-15 17:25 ` Dumitrescu, Cristian
2022-03-15 17:25 ` Singh, Jasvinder
2022-03-15 17:35 ` Thomas Monjalon
2022-03-14 10:47 ` Dumitrescu, Cristian [this message]
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=DM8PR11MB567083D84D0073B9558A6336EB0F9@DM8PR11MB5670.namprd11.prod.outlook.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=john.mcnamara@intel.com \
--cc=megha.ajmera@intel.com \
--cc=sham.singh.thakur@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).