From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 9822C1BAC6 for ; Thu, 10 May 2018 14:29:34 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2018 05:29:33 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,385,1520924400"; d="scan'208";a="54021952" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by fmsmga001.fm.intel.com with ESMTP; 10 May 2018 05:29:32 -0700 Received: from irsmsx107.ger.corp.intel.com ([169.254.10.146]) by IRSMSX103.ger.corp.intel.com ([169.254.3.179]) with mapi id 14.03.0319.002; Thu, 10 May 2018 13:29:31 +0100 From: "Jain, Deepak K" To: "Trahe, Fiona" , "dev@dpdk.org" CC: "De Lara Guarch, Pablo" , "Trahe, Fiona" , "hemant.agrawal@nxp.com" , "shreyansh.jain@nxp.com" Thread-Topic: [dpdk-dev] [PATCH] doc/crypto: add clarification about chained mbuf feature Thread-Index: AQHT4uNIwdXiArgrIES0jrVsjkifaqQo7seg Date: Thu, 10 May 2018 12:29:28 +0000 Deferred-Delivery: Thu, 10 May 2018 12:29:10 +0000 Message-ID: References: <1525354356-31000-1-git-send-email-fiona.trahe@intel.com> In-Reply-To: <1525354356-31000-1-git-send-email-fiona.trahe@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNDA2ZWQxNDItYzZlYy00ZmQ2LTg0NzMtYTdhMzE4MjMwODhlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJBTlJUQjN5XC9McDVQbGc5d0R6OWYwNjR3REUyV1lrR1wvUDJpcExMS3NOMlVnaENNRlhKRzJ5WFBzb25yclYrRHAifQ== dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH] doc/crypto: add clarification about chained mbuf feature X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 May 2018 12:29:35 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fiona Trahe > Sent: Thursday, May 3, 2018 2:33 PM >=20 > 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 >=20 > .. include:: overview_feature_table.txt >=20 > +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 > --------------------------- >=20 > -- > 1.7.0.7 Acked-By: Deepak Kumar Jain