From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 99FFCA0548
	for <public@inbox.dpdk.org>; Fri, 23 Apr 2021 10:59:36 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 902D041DC8;
	Fri, 23 Apr 2021 10:59:36 +0200 (CEST)
Received: from mga07.intel.com (mga07.intel.com [134.134.136.100])
 by mails.dpdk.org (Postfix) with ESMTP id CDB804014F;
 Fri, 23 Apr 2021 10:59:33 +0200 (CEST)
IronPort-SDR: ZsoGu/ZlbE9TlGDp+QElfih1o4zETtwLGumA3L3Jh5WTZWrA13WP6pphp91ljEQXr3OHVxOdT5
 j0bHuZtaED6w==
X-IronPort-AV: E=McAfee;i="6200,9189,9962"; a="259992968"
X-IronPort-AV: E=Sophos;i="5.82,245,1613462400"; d="scan'208";a="259992968"
Received: from orsmga001.jf.intel.com ([10.7.209.18])
 by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
 23 Apr 2021 01:59:32 -0700
IronPort-SDR: HuZupStY67T81sEWYFOL7tbMomAZLaKP+TfX1nEwyFBYMbuLokcGtOEfg7Ei5dd6M5n1gKy/PO
 Zw83tMr/ns9A==
X-IronPort-AV: E=Sophos;i="5.82,245,1613462400"; d="scan'208";a="464258148"
Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.213.255.228])
 ([10.213.255.228])
 by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
 23 Apr 2021 01:59:30 -0700
To: Igor Ryzhov <iryzhov@nfware.com>, Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
 Elad Nachman <eladv6@gmail.com>, dev <dev@dpdk.org>,
 dpdk stable <stable@dpdk.org>, Dan Gora <dg@adax.com>
References: <20201126144613.4986-1-eladv6@gmail.com>
 <b421b26d-0949-3277-2c00-5a7f287c2dd2@intel.com>
 <CACXF7qnUuiqAq7B2S4s1kOnEXwG2cGmV0wdNKYgxS+YXuqXj2g@mail.gmail.com>
 <2345640.QMWomeNEm9@thomas>
 <CAF+s_FxYtSoKmO1Zko05qZymzGbHjW5EZXOgf7Xfufe3ru6q5w@mail.gmail.com>
From: Ferruh Yigit <ferruh.yigit@intel.com>
X-User: ferruhy
Message-ID: <599cc2f5-467a-a954-29be-e77e3b796784@intel.com>
Date: Fri, 23 Apr 2021 09:59:27 +0100
MIME-Version: 1.0
In-Reply-To: <CAF+s_FxYtSoKmO1Zko05qZymzGbHjW5EZXOgf7Xfufe3ru6q5w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v5 3/3] kni: fix kernel
 deadlock when using mlx devices
X-BeenThere: stable@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: patches for DPDK stable branches <stable.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/stable>,
 <mailto:stable-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/stable/>
List-Post: <mailto:stable@dpdk.org>
List-Help: <mailto:stable-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/stable>,
 <mailto:stable-request@dpdk.org?subject=subscribe>
Errors-To: stable-bounces@dpdk.org
Sender: "stable" <stable-bounces@dpdk.org>

On 4/23/2021 9:41 AM, Igor Ryzhov wrote:
> This patch changes the behavior for KNI interface shutdown.
> Previously we would receive a real response from the driver, now we 
> always receive success.
> I think this should be reflected in the docs/release notes.
> 

Hi Igor,

Make sense, I can add it.

Meanwhile do you think has a benefit to make shutdown behavior configurable? 
Async/Sync shutdown based on module param?

> Igor
> 
> On Wed, Apr 21, 2021 at 2:07 AM Thomas Monjalon <thomas@monjalon.net 
> <mailto:thomas@monjalon.net>> wrote:
> 
>     12/04/2021 16:35, Elad Nachman:
>      > Hi,
>      >
>      > The new patch is fine by me.
>      >
>      > Tested several dozens restarts of our proprietary application without
>      > apparent problem.
> 
>     Series applied, thanks.
> 
>