DPDK patches and discussions
 help / color / mirror / Atom feed
From: Megha Ajmera <megha.ajmera@intel.com>
To: dev@dpdk.org, jasvinder.singh@intel.com,
	cristian.dumitrescu@intel.com, thomas@monjalon.net
Subject: [PATCH v1 0/4] sched: HQoS Library cleanup.
Date: Fri, 18 Feb 2022 07:41:44 +0000	[thread overview]
Message-ID: <20220218074148.2549134-1-megha.ajmera@intel.com> (raw)

v1: 
* Removed unused HQoS #defines from rte_config.
* Enabled stats in HQoS by default.
* TC subscription for best effort queues is always enabled in HQoS library.
* VECTOR defines are removed from HQoS library.


Megha Ajmera (4):
  sched: Cleanup qos scheduler defines from rte_config
  sched: Always enable stats in HQoS library.
  sched: Always enable best effort TC oversubscription in HQoS library.
  sched: Removed code defined under VECTOR #Defines.

 config/rte_config.h                        |   7 -
 doc/guides/sample_app_ug/qos_scheduler.rst |   3 +-
 lib/sched/rte_sched.c                      | 156 +--------------------
 3 files changed, 3 insertions(+), 163 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-02-18  7:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18  7:41 Megha Ajmera [this message]
2022-02-18  7:41 ` [PATCH v1 1/4] sched: Cleanup qos scheduler defines from rte_config Megha Ajmera
2022-02-18 16:23   ` Stephen Hemminger
2022-02-18  7:41 ` [PATCH v1 2/4] sched: Always enable stats in HQoS library Megha Ajmera
2022-02-18  7:41 ` [PATCH v1 3/4] sched: Always enable best effort TC oversubscription " Megha Ajmera
2022-02-18  7:41 ` [PATCH v1 4/4] sched: Removed code defined under VECTOR Defines Megha Ajmera
2022-02-18  8:11 ` [PATCH v1 0/4] sched: HQoS Library cleanup David Marchand
2022-02-18  9:41   ` Ajmera, Megha

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=20220218074148.2549134-1-megha.ajmera@intel.com \
    --to=megha.ajmera@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --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).