From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <huawei.xie@intel.com>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id 0EB3793FE
 for <dev@dpdk.org>; Tue, 10 May 2016 10:21:53 +0200 (CEST)
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by fmsmga104.fm.intel.com with ESMTP; 10 May 2016 01:21:53 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.24,604,1455004800"; d="scan'208";a="100366851"
Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206])
 by fmsmga004.fm.intel.com with ESMTP; 10 May 2016 01:21:53 -0700
Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by
 FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Tue, 10 May 2016 01:21:52 -0700
Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by
 fmsmsx120.amr.corp.intel.com (10.18.124.208) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Tue, 10 May 2016 01:21:52 -0700
Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.148]) by
 SHSMSX151.ccr.corp.intel.com ([169.254.3.116]) with mapi id 14.03.0248.002;
 Tue, 10 May 2016 16:21:51 +0800
From: "Xie, Huawei" <huawei.xie@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>, "dev@dpdk.org" <dev@dpdk.org>
CC: "Michael S. Tsirkin" <mst@redhat.com>
Thread-Topic: [PATCH 4/6] vhost: workaround stale vring base
Thread-Index: AdGqlQA6S/uehSl3TSCesgK09fe49Q==
Date: Tue, 10 May 2016 08:21:50 +0000
Message-ID: <C37D651A908B024F974696C65296B57B4C75709E@SHSMSX101.ccr.corp.intel.com>
References: <1462603224-29510-1-git-send-email-yuanhan.liu@linux.intel.com>
 <1462603224-29510-5-git-send-email-yuanhan.liu@linux.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [PATCH 4/6] vhost: workaround stale vring base
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 10 May 2016 08:21:54 -0000

On 5/7/2016 2:36 PM, Yuanhan Liu wrote:=0A=
> When DPDK app crashes (or quits, or gets killed), and when QEMU supports=
=0A=
> reconnecting (patches have been sent, not merged yet), a restart of DPDK=
=0A=
> app would get stale vring base from QEMU. That would break the kernel=0A=
> virtio net completely, making it non-work any more, unless a driver reset=
=0A=
> is done.=0A=
=0A=
s/DPDK app/DPDK vhost/=0A=
=0A=
DPDK app is confusing=0A=
=0A=
>=0A=
> So, instead of getting the stale vring base from QEMU, Huawei suggested=
=0A=
> we could get a proper one from used->idx.=0A=
>=0A=
> Cc: "Michael S. Tsirkin" <mst@redhat.com>=0A=
> Suggested-by: "Xie, Huawei" <huawei.xie@intel.com>=0A=
> Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>=0A=
=0A=
Acked-by: Huawei Xie <huawei.xie@intel.com>=0A=