patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: shahafs <shahafs@mellanox.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix send for multi segment packet
Date: Wed, 21 Dec 2016 17:58:36 +0800	[thread overview]
Message-ID: <20161221095836.GW18991@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <1482310271-45009-1-git-send-email-shahafs@mellanox.com>

On Wed, Dec 21, 2016 at 10:51:11AM +0200, shahafs wrote:
> Fixes: 2a66cf378954 ("net/mlx5: support inline send")
> 
> CC: stable@dpdk.org
> Signed-off-by: shahafs <shahafs@mellanox.com>

I didn't see you cc dev@dpdk.org. Is it a patch only for stable branch
(v16.11 specifically)? And it will not apply to the current master?

	--yliu

> ---
>  drivers/net/mlx5/mlx5_rxtx.c | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_rxtx.c b/drivers/net/mlx5/mlx5_rxtx.c
> index b542e76..8b54651 100644
> --- a/drivers/net/mlx5/mlx5_rxtx.c
> +++ b/drivers/net/mlx5/mlx5_rxtx.c
> @@ -477,7 +477,7 @@
>  				assert(addr <= addr_end);
>  			}
>  			/*
> -			 * 2 DWORDs consumed by the WQE header + 1 DSEG +
> +			 * 2 DWORDs consumed by the WQE header + ETH segment +
>  			 * the size of the inline part of the packet.
>  			 */
>  			ds = 2 + MLX5_WQE_DS(pkt_inline_sz - 2);
> @@ -492,6 +492,10 @@
>  			} else if (!segs_n) {
>  				goto next_pkt;
>  			} else {
> +				/* dseg will be advance as part of next_seg*/
> +				dseg = (volatile rte_v128u32_t *)
> +					((uintptr_t)wqe +
> +					 ((ds-1) * MLX5_WQE_DWORD_SIZE));
>  				goto next_seg;
>  			}
>  		} else {
> -- 
> 1.8.3.1

  reply	other threads:[~2016-12-21  9:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  8:51 shahafs
2016-12-21  9:58 ` Yuanhan Liu [this message]
2016-12-21 13:04   ` Shahaf Shuler

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=20161221095836.GW18991@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=shahafs@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).