DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Chautru, Nicolas" <nicolas.chautru@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
	"trix@redhat.com" <trix@redhat.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/7] BBDEV test updates
Date: Wed, 7 Oct 2020 00:13:06 +0000	[thread overview]
Message-ID: <BY5PR11MB4451ADA2B701F3C54FCA4D84F80A0@BY5PR11MB4451.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1597795557-39612-1-git-send-email-nicolas.chautru@intel.com>

Hi Akhil, 
Just a heads up on this bbdev related serie in case you missed it. 
It would be useful to have all the bbdev changes into rc1. 
+ Tom
Thanks again, 
Nic


> -----Original Message-----
> From: Chautru, Nicolas <nicolas.chautru@intel.com>
> Sent: Tuesday, August 18, 2020 5:06 PM
> To: dev@dpdk.org; akhil.goyal@nxp.com
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; Chautru, Nicolas
> <nicolas.chautru@intel.com>
> Subject: [PATCH v3 0/7] BBDEV test updates
> 
> v3: apologize again for typo and not double checking with check-git-log
> v2: typos missed in commit messages
> Serie updating and extending the app running the bbdev-test for the existing
> bbdev PMDs.
> 
> 
> Nicolas Chautru (7):
>   app/bbdev: add explicit ut for latency vs validation
>   app/bbdev: add explicit check for counters
>   app/bbdev: include explicit HARQ preloading
>   app/bbdev: define wait for offload
>   app/bbdev: skip bler ut when compression is used
>   app/bbdev: reduce duration of throughput test
>   app/bbdev: update offload test to dequeue full ring
> 
>  app/test-bbdev/main.h            |   1 +
>  app/test-bbdev/test_bbdev_perf.c | 193
> ++++++++++++++++++++++++++++++---------
>  2 files changed, 152 insertions(+), 42 deletions(-)
> 
> --
> 1.8.3.1


  parent reply	other threads:[~2020-10-07  0:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19  0:05 Nicolas Chautru
2020-08-19  0:05 ` [dpdk-dev] [PATCH v3 1/7] app/bbdev: add explicit ut for latency vs validation Nicolas Chautru
2020-09-15  9:49   ` Aidan Goddard
2020-09-15 10:01   ` Dave Burley
2020-08-19  0:05 ` [dpdk-dev] [PATCH v3 2/7] app/bbdev: add explicit check for counters Nicolas Chautru
2020-09-15  9:53   ` Aidan Goddard
2020-09-15 10:02   ` Dave Burley
2020-08-19  0:05 ` [dpdk-dev] [PATCH v3 3/7] app/bbdev: include explicit HARQ preloading Nicolas Chautru
2020-08-19  0:05 ` [dpdk-dev] [PATCH v3 4/7] app/bbdev: define wait for offload Nicolas Chautru
2020-08-19  0:05 ` [dpdk-dev] [PATCH v3 5/7] app/bbdev: skip bler ut when compression is used Nicolas Chautru
2020-09-15  9:55   ` Aidan Goddard
2020-09-15 10:03   ` Dave Burley
2020-08-19  0:05 ` [dpdk-dev] [PATCH v3 6/7] app/bbdev: reduce duration of throughput test Nicolas Chautru
2020-08-19  0:05 ` [dpdk-dev] [PATCH v3 7/7] app/bbdev: update offload test to dequeue full ring Nicolas Chautru
2020-09-15  9:55   ` Aidan Goddard
2020-09-15 10:05   ` Dave Burley
2020-10-07  0:13 ` Chautru, Nicolas [this message]
2020-10-07  6:37   ` [dpdk-dev] [PATCH v3 0/7] BBDEV test updates Akhil Goyal
2020-10-07 16:00     ` Chautru, Nicolas
2020-10-20 16:08     ` Chautru, Nicolas

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=BY5PR11MB4451ADA2B701F3C54FCA4D84F80A0@BY5PR11MB4451.namprd11.prod.outlook.com \
    --to=nicolas.chautru@intel.com \
    --cc=akhil.goyal@nxp.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=trix@redhat.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).