DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
	Long Wu <long.wu@corigine.com>,
	jin.liu@corigine.com, stable@dpdk.org
Subject: Re: [PATCH v2] net/nfp: fix issue of data len exceeds descriptor limitation
Date: Wed, 7 Dec 2022 12:28:04 +0000	[thread overview]
Message-ID: <9b41c93f-579c-34e0-3611-abe77576e9c5@amd.com> (raw)
In-Reply-To: <20221129012122.24394-1-chaoyong.he@corigine.com>

On 11/29/2022 1:21 AM, Chaoyong He wrote:
> From: Long Wu <long.wu@corigine.com>
> 
> If dma_len is larger than NFDK_DESC_TX_DMA_LEN_HEAD, the value of
> dma_len bitwise and NFDK_DESC_TX_DMA_LEN_HEAD maybe less than packet
> head length and the packet will be dropped. Fill maximum dma_len in
> first tx descriptor to make sure the whole head is included in the
> first descriptor. In addition, add comments to better explain the
> code flow.
> 

updated patch title as:
net/nfp: fix Tx packet drop for large data length

> Fixes: c73dced48c8c ("net/nfp: add NFDk Tx")
> Cc: jin.liu@corigine.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Long Wu <long.wu@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>

Applied to dpdk-next-net/main, thanks.


Below changes done while merging.

> +		/*
> +		 * We will do our best to pass as much data as we can in descriptor
> +		 * and we need to make sure the first descriptor includes whole
> +		 * head since there is limitation in firmware side. Sometimes the
> +		 * value of dma_len bitwise & NFDK_DESC_TX_DMA_LEN_HEAD will less
> +		 * than packet head len.
> +		 */

Updated last line as:
" * value of 'dma_len & NFDK_DESC_TX_DMA_LEN_HEAD' will be less "

<...>

>  
> +		/*
> +		 * The rest of the data (if any) will be in larger dma descritors

s/descritors/descriptors/
s/dma/DMA/


      reply	other threads:[~2022-12-07 12:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17  8:33 [PATCH] " Chaoyong He
2022-11-18 11:14 ` Ferruh Yigit
2022-11-29  1:21 ` [PATCH v2] " Chaoyong He
2022-12-07 12:28   ` Ferruh Yigit [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=9b41c93f-579c-34e0-3611-abe77576e9c5@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=jin.liu@corigine.com \
    --cc=long.wu@corigine.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.com \
    --cc=stable@dpdk.org \
    /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).