From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v2 0/4] fixes for dma/idxd
Date: Tue, 11 Jan 2022 13:41:01 +0000 [thread overview]
Message-ID: <20220111134105.1007191-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20211220170514.736732-1-bruce.richardson@intel.com>
Collection of fixes for idxd driver, including one small enhancement to the
unit tests to help catch future errors too.
V2:
* Changed from single patch for one issue (now patch 1) to multiple
patches to cover other issues discovered.
Bruce Richardson (4):
dma/idxd: fix burst capacity calculation
dma/idxd: fix paths to driver sysfs directory
dma/idxd: fix wrap-around in burst capacity calculation
test_dmadev: increase iterations of capacity test case
app/test/test_dmadev.c | 7 ++++---
drivers/dma/idxd/dpdk_idxd_cfg.py | 18 ++++++++++++++----
drivers/dma/idxd/idxd_common.c | 10 +++++-----
3 files changed, 23 insertions(+), 12 deletions(-)
--
2.32.0
next prev parent reply other threads:[~2022-01-11 13:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 17:05 [PATCH] dma/idxd: fix burst capacity calculation Bruce Richardson
2022-01-04 17:16 ` Kevin Laatz
2022-01-05 1:32 ` Hu, Jiayu
2022-01-10 13:09 ` Pai G, Sunil
2022-01-10 13:25 ` Bruce Richardson
2022-01-10 13:44 ` Pai G, Sunil
2022-01-10 16:18 ` Bruce Richardson
2022-01-11 13:41 ` Bruce Richardson [this message]
2022-01-11 13:41 ` [PATCH v2 1/4] " Bruce Richardson
2022-01-11 13:41 ` [PATCH v2 2/4] dma/idxd: fix paths to driver sysfs directory Bruce Richardson
2022-01-11 16:50 ` Kevin Laatz
2022-01-11 13:41 ` [PATCH v2 3/4] dma/idxd: fix wrap-around in burst capacity calculation Bruce Richardson
2022-01-11 13:45 ` Pai G, Sunil
2022-01-11 16:50 ` Kevin Laatz
2022-01-11 13:41 ` [PATCH v2 4/4] test_dmadev: increase iterations of capacity test case Bruce Richardson
2022-01-11 16:50 ` Kevin Laatz
2022-01-20 13:06 ` [PATCH v2 0/4] fixes for dma/idxd 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=20220111134105.1007191-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).