From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <changchun.ouyang@intel.com>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id BDADB68BE
 for <dev@dpdk.org>; Fri, 12 Dec 2014 02:02:29 +0100 (CET)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by orsmga101.jf.intel.com with ESMTP; 11 Dec 2014 17:02:28 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.07,560,1413270000"; d="scan'208";a="652589884"
Received: from kmsmsx151.gar.corp.intel.com ([172.21.73.86])
 by orsmga002.jf.intel.com with ESMTP; 11 Dec 2014 17:02:27 -0800
Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by
 KMSMSX151.gar.corp.intel.com (172.21.73.86) with Microsoft SMTP Server (TLS)
 id 14.3.195.1; Fri, 12 Dec 2014 09:00:45 +0800
Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.216]) by
 SHSMSX151.ccr.corp.intel.com ([169.254.3.67]) with mapi id 14.03.0195.001;
 Fri, 12 Dec 2014 09:00:27 +0800
From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "Fu, Weiyi (NSN - CN/Hangzhou)" <weiyi.fu@nsn.com>, "dev@dpdk.org"
 <dev@dpdk.org>
Thread-Topic: [dpdk-dev]  In DPDK 1.7.1, the link status of the interface
 using virtio driver is always down.
Thread-Index: AdAVGAyqYy44KGUjQTy/NjxEYje2g5yKEnVAgAAxdTCciSci4A==
Date: Fri, 12 Dec 2014 01:00:26 +0000
Message-ID: <F52918179C57134FAEC9EA62FA2F962511945B8E@shsmsx102.ccr.corp.intel.com>
References: <2680B515A539A446ACBEC0EBBDEC3DF80E938312@SGSIMBX001.nsn-intra.net>
 <F52918179C57134FAEC9EA62FA2F9625119456D4@shsmsx102.ccr.corp.intel.com>
 <2680B515A539A446ACBEC0EBBDEC3DF80E938465@SGSIMBX001.nsn-intra.net>
In-Reply-To: <2680B515A539A446ACBEC0EBBDEC3DF80E938465@SGSIMBX001.nsn-intra.net>
Accept-Language: zh-CN, 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] In DPDK 1.7.1,
 the link status of the interface using virtio driver is always down.
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: Fri, 12 Dec 2014 01:02:34 -0000

Hi=20

> -----Original Message-----
> From: Fu, Weiyi (NSN - CN/Hangzhou) [mailto:weiyi.fu@nsn.com]
> Sent: Thursday, December 11, 2014 7:42 PM
> To: Fu, Weiyi (NSN - CN/Hangzhou); Ouyang, Changchun; dev@dpdk.org
> Subject: RE: [dpdk-dev] In DPDK 1.7.1, the link status of the interface u=
sing
> virtio driver is always down.
>=20
> Hi Changchun,
> I found you had done follow change to allow the virtio interface startup
> when the link is down.  Is there any scenario causing link down for virti=
o
> interface?
>=20
Not really in my environment, those codes are RFC codes from Brocade,
Not merged into mainline yet.=20

You can apply this patch and ignore the link state to see if rx and tx stil=
l works.

Thanks
Changchun