From: "Jain, Deepak K" <deepak.k.jain@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] doc/crypto: add clarification about chained mbuf feature
Date: Thu, 10 May 2018 12:29:28 +0000 [thread overview]
Message-ID: <A09C9DDE180C7E429EC68E2BFB95C9037D09456E@IRSMSX107.ger.corp.intel.com> (raw)
In-Reply-To: <1525354356-31000-1-git-send-email-fiona.trahe@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fiona Trahe
> Sent: Thursday, May 3, 2018 2:33 PM
>
> diff --git a/doc/guides/cryptodevs/overview.rst
> b/doc/guides/cryptodevs/overview.rst
> index b3cb6ca..493cd5f 100644
> --- a/doc/guides/cryptodevs/overview.rst
> +++ b/doc/guides/cryptodevs/overview.rst
> @@ -11,6 +11,16 @@ Supported Feature Flags
>
> .. include:: overview_feature_table.txt
>
> +Note, the mbuf scatter gather feature (aka chained mbufs,
> +scatter-gather-lists or SGLs) indicate all following combinations are
> +supported unless otherwise called out in the Limitations section of each
> PMD.
> +
> +* In place operation, input buffer as multiple segments, same buffer
> +used for output
> +* Out of place operation, input buffer as single segment and output as
> +multiple segments
> +* Out of place operation, input buffer as multiple segments and output
> +as single segment
> +* Out of place operation, input buffer as multiple segments and output
> +as multiple segments
> +
> +
> Supported Cipher Algorithms
> ---------------------------
>
> --
> 1.7.0.7
Acked-By: Deepak Kumar Jain <Deepak.k.jain@intel.com>
next prev parent reply other threads:[~2018-05-10 12:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 13:32 Fiona Trahe
2018-05-10 12:29 ` Jain, Deepak K [this message]
2018-05-21 21:59 ` De Lara Guarch, Pablo
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=A09C9DDE180C7E429EC68E2BFB95C9037D09456E@IRSMSX107.ger.corp.intel.com \
--to=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=shreyansh.jain@nxp.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).