From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Daly, Lee" <lee.daly@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4] compress/isal: add chained mbuf support
Date: Tue, 24 Jul 2018 13:36:28 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8977F90073F@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D8977F900705@IRSMSX107.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of De Lara Guarch, Pablo
> Sent: Tuesday, July 24, 2018 2:28 PM
> To: Daly, Lee <lee.daly@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v4] compress/isal: add chained mbuf support
>
>
>
> > -----Original Message-----
> > From: Daly, Lee
> > Sent: Tuesday, July 24, 2018 12:19 PM
> > To: De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>
> > Cc: dev@dpdk.org; Daly, Lee <lee.daly@intel.com>
> > Subject: [PATCH v4] compress/isal: add chained mbuf support
> >
> > This patch adds chained mbuf support for input or output buffers
> > during compression/decompression operations.
> >
> > V2 - split chained mbuf functionality into separate functions.
> > - code optimizations.
> >
> > V3 - bug fixes & optimizations.
> >
> > v4 - bug fixes & optimizations.
> >
> > Signed-off-by: Lee Daly <lee.daly@intel.com>
>
> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2018-07-24 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 11:03 [dpdk-dev] [PATCH] " Lee Daly
2018-07-11 12:40 ` [dpdk-dev] [PATCH v2] " Lee, Daly
2018-07-20 10:38 ` De Lara Guarch, Pablo
2018-07-23 18:02 ` [dpdk-dev] [PATCH v3] " Daly, Lee
2018-07-23 21:14 ` De Lara Guarch, Pablo
2018-07-24 11:19 ` [dpdk-dev] [PATCH v4] " Daly, Lee
2018-07-24 13:27 ` De Lara Guarch, Pablo
2018-07-24 13:36 ` De Lara Guarch, Pablo [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8977F90073F@IRSMSX107.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=lee.daly@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 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).