From: Yongseok Koh <yskoh@mellanox.com>
To: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix updating total length of multi-packet send
Date: Fri, 13 Jan 2017 19:55:36 +0000 [thread overview]
Message-ID: <3FEDCB07-DF42-4E44-A839-BDD390FD0656@mellanox.com> (raw)
In-Reply-To: <20170113194537.19364-1-yskoh@mellanox.com>
Hi
It was my mistake to send it to only stable@dpdk.org. I should've included
dev@dpdk.org and the maintainer. I will send it again appropriately, please
ignore this email.
Thanks,
Yongseok
> On Jan 13, 2017, at 11:45 AM, Yongseok Koh <yskoh@mellanox.com> wrote:
>
> The total length field in descriptor of inlined multi-packet send must be
> updated before closing a seesion. There's possibility of updating it
> afterward. This bug might cause one packet out of MLX5_MPW_DSEG_MAX gets
> silently dropped by HW and impact performance, escpecially lossless test..
>
> Fixes: 230189d9ff22 ("net/mlx5: support multi-packet send")
>
> CC: stable@dpdk.org
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
> ---
> drivers/net/mlx5/mlx5_rxtx.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/mlx5/mlx5_rxtx.c b/drivers/net/mlx5/mlx5_rxtx.c
> index 89b1300e6..a5b492dcc 100644
> --- a/drivers/net/mlx5/mlx5_rxtx.c
> +++ b/drivers/net/mlx5/mlx5_rxtx.c
> @@ -1179,6 +1179,7 @@ mlx5_tx_burst_mpw_inline(void *dpdk_txq, struct rte_mbuf **pkts,
> mpw.data.raw += length;
> }
> ++mpw.pkts_n;
> + mpw.total_len += length;
> ++j;
> if (mpw.pkts_n == MLX5_MPW_DSEG_MAX) {
> mlx5_mpw_inline_close(txq, &mpw);
> @@ -1188,7 +1189,6 @@ mlx5_tx_burst_mpw_inline(void *dpdk_txq, struct rte_mbuf **pkts,
> inline_room -= length;
> }
> }
> - mpw.total_len += length;
> elts_head = elts_head_next;
> #ifdef MLX5_PMD_SOFT_COUNTERS
> /* Increment sent bytes counter. */
> --
> 2.11.0
>
next prev parent reply other threads:[~2017-01-13 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 19:45 Yongseok Koh
2017-01-13 19:55 ` Yongseok Koh [this message]
2017-02-02 18:43 Yongseok Koh
2017-02-08 14:28 ` Nélio Laranjeiro
2017-02-08 15:37 ` Ferruh Yigit
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=3FEDCB07-DF42-4E44-A839-BDD390FD0656@mellanox.com \
--to=yskoh@mellanox.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).