All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/4] fixes and improvements for rawdev
Date: Fri, 21 Jun 2019 16:56:55 +0100	[thread overview]
Message-ID: <20190621155659.29297-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20190619170802.7691-1-bruce.richardson@intel.com>

This set includes some general fixes and improvements for rawdev, the
rawdev autotests and the rawdev skeleton example implementation.
Specifically:

* the unit test were failing for me due to bad memory management
* the unit tests were not present in the meson builds due to missing
  file in file list
* the self-test function for a rawdev driver did not take the actual
  device id as a parameter:
  - because of this the skeleton driver always assumed device 0 was to
    be tested, an unsafe assumption

V2:
	extended the set with additional fixes to allow selftests to know
	what instance the tests are to be run on.

Bruce Richardson (4):
  raw/skeleton: fix failing test case
  app/test: add missing rawdev autotest to meson build
  raw/skeleton: remove compile-time constant for device id
  rawdev: pass the device id as parameter to selftest

 app/test/meson.build                          |  3 +
 drivers/raw/skeleton_rawdev/skeleton_rawdev.c |  8 ++-
 drivers/raw/skeleton_rawdev/skeleton_rawdev.h |  2 +-
 .../skeleton_rawdev/skeleton_rawdev_test.c    | 66 +++++++++----------
 lib/librte_rawdev/rte_rawdev.c                |  2 +-
 lib/librte_rawdev/rte_rawdev_pmd.h            |  2 +-
 6 files changed, 43 insertions(+), 40 deletions(-)

-- 
2.21.0


  parent reply	other threads:[~2019-06-21 15:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 17:08 [dpdk-dev] [PATCH 0/2] rawdev autotest fixes Bruce Richardson
2019-06-19 17:08 ` [dpdk-dev] [PATCH 1/2] raw/skeleton: fix failing test case Bruce Richardson
2019-06-19 17:08 ` [dpdk-dev] [PATCH 2/2] app/test: add missing rawdev autotest to meson build Bruce Richardson
2019-06-21 15:56 ` Bruce Richardson [this message]
2019-06-21 15:56   ` [dpdk-dev] [PATCH v2 1/4] raw/skeleton: fix failing test case Bruce Richardson
2019-06-27 11:50     ` Hemant Agrawal
2019-07-01 18:03     ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-06-21 15:56   ` [dpdk-dev] [PATCH v2 2/4] app/test: add missing rawdev test to meson build Bruce Richardson
2019-07-01 18:10     ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-06-21 15:56   ` [dpdk-dev] [PATCH v2 3/4] raw/skeleton: remove compile-time constant for device id Bruce Richardson
2019-06-21 15:56   ` [dpdk-dev] [PATCH v2 4/4] rawdev: pass device id as parameter to selftest Bruce Richardson
2019-07-04  9:33     ` Shreyansh Jain
2019-07-02  9:56 ` [dpdk-dev] [PATCH v3 0/3] fixes and improvements for rawdev Bruce Richardson
2019-07-02  9:56   ` [dpdk-dev] [PATCH v3 1/3] app/test: add missing rawdev autotest to meson build Bruce Richardson
2019-07-02  9:56   ` [dpdk-dev] [PATCH v3 2/3] raw/skeleton: remove compile-time constant for device id Bruce Richardson
2019-07-02  9:56   ` [dpdk-dev] [PATCH v3 3/3] rawdev: pass the device id as parameter to selftest Bruce Richardson
2019-07-02 15:05   ` [dpdk-dev] [PATCH v3 0/3] fixes and improvements for rawdev 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=20190621155659.29297-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 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.