DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Verma, Shally" <Shally.Verma@cavium.com>
To: Fiona Trahe <fiona.trahe@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
	"Gupta,  Ashish" <Ashish.Gupta@cavium.com>,
	"Sahu, Sunila" <Sunila.Sahu@cavium.com>
Subject: Re: [dpdk-dev] [PATCH] compressdev: clarify buffer size limitation
Date: Thu, 17 May 2018 06:10:29 +0000	[thread overview]
Message-ID: <CY4PR0701MB36345AC5B4270B5A1004A8C3F0910@CY4PR0701MB3634.namprd07.prod.outlook.com> (raw)
In-Reply-To: <1526480339-13056-1-git-send-email-fiona.trahe@intel.com>



>-----Original Message-----
>From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Fiona Trahe
>Sent: 16 May 2018 19:49
>To: dev@dpdk.org
>Cc: pablo.de.lara.guarch@intel.com; fiona.trahe@intel.com
>Subject: [dpdk-dev] [PATCH] compressdev: clarify buffer size limitation
>
>Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
>---
> lib/librte_compressdev/rte_comp.h | 11 +++++++++--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
>diff --git a/lib/librte_compressdev/rte_comp.h b/lib/librte_compressdev/rte_comp.h
>index 4c802195f..9826086b1 100644
>--- a/lib/librte_compressdev/rte_comp.h
>+++ b/lib/librte_compressdev/rte_comp.h
>@@ -295,12 +295,19 @@ struct rte_comp_op {
> 	struct rte_mbuf *m_src;
> 	/**< source mbuf
> 	 * The total size of the input buffer(s) can be retrieved using
>-	 * rte_pktmbuf_data_len(m_src)
>+	 * rte_pktmbuf_data_len(m_src). The max data size which can fit in a
>+	 * single mbuf is limited by the uint16_t rte_mbuf.data_len to 64k-1.
>+	 * If the input data is bigger than this it can be passed to the PMD in
>+	 * a chain of mbufs if the PMD's capabilities indicate it supports this.
> 	 */
> 	struct rte_mbuf *m_dst;
> 	/**< destination mbuf
> 	 * The total size of the output buffer(s) can be retrieved using
>-	 * rte_pktmbuf_data_len(m_dst)
>+	 * rte_pktmbuf_data_len(m_dst). The max data size which can fit in a
>+	 * single mbuf is limited by the uint16_t rte_mbuf.data_len to 64k-1.
>+	 * If the output data is expected to be bigger than this a chain of
>+	 * mbufs can be passed to the PMD if the PMD's capabilities indicate
>+	 * it supports this.
> 	 */
[Shally] It will be good idea to add bit more clarification regarding src.offset and dst.offset as well, that is, offset is offset from start of very first segment of m_src and m_dst in chained bufs.

>
> 	struct {
>--
>2.13.6

  reply	other threads:[~2018-05-17  6:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 14:18 Fiona Trahe
2018-05-17  6:10 ` Verma, Shally [this message]
2018-05-21 22:32   ` De Lara Guarch, Pablo
2018-05-22 10:08     ` 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=CY4PR0701MB36345AC5B4270B5A1004A8C3F0910@CY4PR0701MB3634.namprd07.prod.outlook.com \
    --to=shally.verma@cavium.com \
    --cc=Ashish.Gupta@cavium.com \
    --cc=Sunila.Sahu@cavium.com \
    --cc=dev@dpdk.org \
    --cc=fiona.trahe@intel.com \
    --cc=pablo.de.lara.guarch@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).