All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akhil Goyal <akhil.goyal@nxp.com>
To: Tomasz Cel <tomaszx.cel@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
	"fiona.trahe@intel.com" <fiona.trahe@intel.com>,
	"tomaszx.jozwiak@intel.com" <tomaszx.jozwiak@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 0/1] add max mbuf size test case
Date: Tue, 16 Apr 2019 14:53:52 +0000	[thread overview]
Message-ID: <VI1PR04MB4893096398DD9D41A23155CFE6240@VI1PR04MB4893.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <1554207413-19049-1-git-send-email-tomaszx.cel@intel.com>



> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Tomasz Cel
> Sent: Tuesday, April 2, 2019 5:47 PM
> To: dev@dpdk.org; fiona.trahe@intel.com; tomaszx.jozwiak@intel.com;
> tomaszx.cel@intel.com
> Subject: [dpdk-dev] [PATCH v2 0/1] add max mbuf size test case
> 
> From: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>
> 
> This patch adds new test case in which max. size of
> chain mbufs has been used to compress random data dynamically.
> 
> V2 changes:
> 
>   Added changes to new test_compressdev.c file location
>   in app/test/ folder
> 
> Tomasz Jozwiak (1):
>   test/compress: add max mbuf size test case
> 
>  app/test/test_compressdev.c | 158
> ++++++++++++++++++++++++++++++++++++++------
>  1 file changed, 136 insertions(+), 22 deletions(-)
Applied to dpdk-next-crypto

Thanks.

  parent reply	other threads:[~2019-04-16 14:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15  9:44 [PATCH] compress/qat: add dynamic sgl allocation Tomasz Jozwiak
2019-02-15  9:44 ` [PATCH] compress/qat: add fallback to fixed compression Tomasz Jozwiak
2019-02-15 17:01   ` Trahe, Fiona
2019-03-19 14:04     ` Akhil Goyal
2019-02-15  9:44 ` [PATCH] test/compress: add max mbuf size test case Tomasz Jozwiak
2019-03-27 14:02   ` Akhil Goyal
2019-04-02 12:16   ` [PATCH v2 0/1] " Tomasz Cel
2019-04-02 12:16     ` [PATCH v2 1/1] test/compress: " Tomasz Cel
2019-04-02 12:22       ` Cel, TomaszX
2019-04-18 22:42         ` [dpdk-dev] " Yongseok Koh
2019-04-19  9:07           ` Thomas Monjalon
2019-04-19  9:25             ` David Marchand
2019-04-19  9:30               ` Thomas Monjalon
2019-04-19  9:32                 ` Jozwiak, TomaszX
2019-04-19  9:39                   ` David Marchand
2019-04-19  9:58           ` Jozwiak, TomaszX
2019-04-16 14:53     ` Akhil Goyal [this message]
2019-03-01 11:00 ` [PATCH v2] add dynamic sgl allocation Tomasz Jozwiak
2019-03-01 11:00   ` [PATCH v2] compress/qat: " Tomasz Jozwiak
2019-03-01 11:17 ` [PATCH v3 0/1] " Tomasz Jozwiak
2019-03-01 11:17   ` [PATCH v3 1/1] compress/qat: " Tomasz Jozwiak
2019-03-07 12:02   ` [PATCH v4 0/1] " Tomasz Jozwiak
2019-03-07 12:02     ` [PATCH v4 1/1] compress/qat: " Tomasz Jozwiak
2019-03-07 18:58       ` Trahe, Fiona
2019-03-17 18:00       ` Akhil Goyal
2019-03-18  8:12         ` Jozwiak, TomaszX
2019-03-18  8:23           ` arpita das
2019-03-26 13:51     ` [PATCH v5 0/1] " Tomasz Jozwiak
2019-03-26 13:51       ` [PATCH v5 1/1] compress/qat: " Tomasz Jozwiak
2019-03-28 14:37         ` Trahe, Fiona
2019-03-29 14:40           ` Akhil Goyal
2019-04-03  8:39             ` Akhil Goyal

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=VI1PR04MB4893096398DD9D41A23155CFE6240@VI1PR04MB4893.eurprd04.prod.outlook.com \
    --to=akhil.goyal@nxp.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=tomaszx.cel@intel.com \
    --cc=tomaszx.jozwiak@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.