DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raslan Darawsheh <rasland@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>, Ori Kam <orika@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix legacy non inline multi packet session
Date: Thu, 13 Feb 2020 11:30:41 +0000	[thread overview]
Message-ID: <a4f23775-4933-940d-ada4-f25de03036c6@intel.com> (raw)
In-Reply-To: <AM0PR05MB6707E4501E6A003DD7D20559C21A0@AM0PR05MB6707.eurprd05.prod.outlook.com>

On 2/13/2020 9:38 AM, Raslan Darawsheh wrote:
> Hi,
> 
>> -----Original Message-----
>> From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
>> Sent: Wednesday, February 12, 2020 7:49 PM
>> To: dev@dpdk.org
>> Cc: Matan Azrad <matan@mellanox.com>; Raslan Darawsheh
>> <rasland@mellanox.com>; Ori Kam <orika@mellanox.com>
>> Subject: [PATCH] net/mlx5: fix legacy non inline multi packet session
>>
>> The commit being fixed introduced the different format
>> for the transmitting descriptor multi-packet session for
>> ConnectX-4LX. The session was assumed always opened if
>> not-inlinable packet was encountered. The patch checks
>> whether the inline multi-packet is opened and it allows
>> to proceed with normal packets (non inlined) successfully.
>>
>> Fixes: 82a506b404b0 ("net/mlx5: fix the legacy multi packet write session")
>>
> Added Cc: stable@dpdk.org
> 
>> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
>> ---
>>  drivers/net/mlx5/mlx5_rxtx.c | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/net/mlx5/mlx5_rxtx.c b/drivers/net/mlx5/mlx5_rxtx.c
>> index 86e0fab..b55db4f 100644
>> --- a/drivers/net/mlx5/mlx5_rxtx.c
>> +++ b/drivers/net/mlx5/mlx5_rxtx.c
>> @@ -4341,6 +4341,7 @@ enum mlx5_txcmp_code {
>>  			 * intermix for legacy MPW sessions.
>>  			 */
>>  			if (MLX5_TXOFF_CONFIG(MPW) &&
>> +			    part != room &&
>>  			    loc->wqe_last->dseg[0].bcount == RTE_BE32(0))
>>  				break;
>>  			/*
>> --
>> 1.8.3.1
> 
> 
> Patch applied next-net-mlx,
> 

Squashed into relevant commit in next-net, thanks.

      reply	other threads:[~2020-02-13 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 17:49 Viacheslav Ovsiienko
2020-02-13  9:38 ` Raslan Darawsheh
2020-02-13 11:30   ` 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=a4f23775-4933-940d-ada4-f25de03036c6@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=rasland@mellanox.com \
    --cc=viacheslavo@mellanox.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).