patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Tom Rix <trix@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>,
	dev@dpdk.org, gakhil@marvell.com
Cc: thomas@monjalon.net, mingshan.zhang@intel.com,
	arun.joshi@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v1] baseband/acc100: fix 4GUL outbound size when CRC is dropped
Date: Sat, 11 Sep 2021 12:18:53 -0700	[thread overview]
Message-ID: <2a661e89-aca6-4924-ff39-8d0da194093d@redhat.com> (raw)
In-Reply-To: <1631065180-18253-1-git-send-email-nicolas.chautru@intel.com>


On 9/7/21 6:39 PM, Nicolas Chautru wrote:
> This patch fixes the issue by adjusting the outbound size after
> turbodecoding when the appended CRC is meant to be dropped.
>
> Fixes: f404dfe35cc3 ("baseband/acc100: support 4G processing")
> Cc: stable@dpdk.org
>
> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
> ---
>   drivers/baseband/acc100/rte_acc100_pmd.c | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/baseband/acc100/rte_acc100_pmd.c b/drivers/baseband/acc100/rte_acc100_pmd.c
> index 68ba523..b0485e7 100644
> --- a/drivers/baseband/acc100/rte_acc100_pmd.c
> +++ b/drivers/baseband/acc100/rte_acc100_pmd.c
> @@ -1744,7 +1744,8 @@
>   
>   	next_triplet = acc100_dma_fill_blk_type_out(
>   			desc, h_output, *h_out_offset,
> -			k >> 3, next_triplet, ACC100_DMA_BLKID_OUT_HARD);
> +			(k - crc24_overlap) >> 3, next_triplet,
> +			ACC100_DMA_BLKID_OUT_HARD);
>   	if (unlikely(next_triplet < 0)) {
>   		rte_bbdev_log(ERR,
>   				"Mismatch between data to process and mbuf data length in bbdev_op: %p",

Thanks for this change, looks good.

Reviewed-by: Tom Rix <trix@redhat.com>



  reply	other threads:[~2021-09-11 19:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-08  1:39 Nicolas Chautru
2021-09-11 19:18 ` Tom Rix [this message]
2021-10-04 23:39   ` Chautru, Nicolas
2021-10-05 10:10     ` Akhil Goyal
2021-10-05 15:12       ` Chautru, Nicolas

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=2a661e89-aca6-4924-ff39-8d0da194093d@redhat.com \
    --to=trix@redhat.com \
    --cc=arun.joshi@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.com \
    --cc=mingshan.zhang@intel.com \
    --cc=nicolas.chautru@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).