From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: jasvinder.singh@intel.com, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 0/4] small fixes and improvements for qos_sched example
Date: Fri, 3 Feb 2023 10:05:29 +0000 [thread overview]
Message-ID: <20230203100533.10377-1-bruce.richardson@intel.com> (raw)
This patchset contains a set of fixes and improvements for the qos_sched
application. After this patchset the code is shorter, and also seems a
little faster in my performance tests.
Bruce Richardson (4):
examples/qos_sched: fix errors when TX port not up
examples/qos_sched: remove TX buffering
examples/qos_sched: use bigger bursts on dequeue
examples/qos_sched: remove limit on core ids
doc/guides/sample_app_ug/qos_scheduler.rst | 2 +-
examples/qos_sched/app_thread.c | 94 +++-------------------
examples/qos_sched/args.c | 72 +----------------
examples/qos_sched/init.c | 10 +++
examples/qos_sched/main.c | 12 ---
examples/qos_sched/main.h | 18 +----
6 files changed, 25 insertions(+), 183 deletions(-)
--
2.37.2
next reply other threads:[~2023-02-03 10:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 10:05 Bruce Richardson [this message]
2023-02-03 10:05 ` [PATCH 1/4] examples/qos_sched: fix errors when TX port not up Bruce Richardson
2023-02-17 16:19 ` Dumitrescu, Cristian
2023-02-03 10:05 ` [PATCH 2/4] examples/qos_sched: remove TX buffering Bruce Richardson
2023-02-17 16:19 ` Dumitrescu, Cristian
2023-02-03 10:05 ` [PATCH 3/4] examples/qos_sched: use bigger bursts on dequeue Bruce Richardson
2023-02-17 16:20 ` Dumitrescu, Cristian
2023-02-03 10:05 ` [PATCH 4/4] examples/qos_sched: remove limit on core ids Bruce Richardson
2023-02-17 16:20 ` Dumitrescu, Cristian
2023-02-20 15:41 ` [PATCH 0/4] small fixes and improvements for qos_sched example 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=20230203100533.10377-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.