From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id B5B7D298F for ; Mon, 24 Oct 2016 11:50:45 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga102.jf.intel.com with ESMTP; 24 Oct 2016 02:50:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,541,1473145200"; d="scan'208";a="1074794734" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga002.fm.intel.com with ESMTP; 24 Oct 2016 02:50:44 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 24 Oct 2016 02:50:44 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.139]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.2]) with mapi id 14.03.0248.002; Mon, 24 Oct 2016 17:50:42 +0800 From: "Wu, Jingjing" To: "Yang, Qiming" , "dev@dpdk.org" CC: "Yang, Qiming" Thread-Topic: [dpdk-dev] [PATCH 2/2] net/i40e: fix VF bonded device link down Thread-Index: AQHSJRiavl1HTlxfN0m0A6epCTtuaKC3apug Date: Mon, 24 Oct 2016 09:50:40 +0000 Message-ID: <9BB6961774997848B5B42BEC655768F80E293AE1@SHSMSX103.ccr.corp.intel.com> References: <1476338840-50003-1-git-send-email-qiming.yang@intel.com> <1476338840-50003-2-git-send-email-qiming.yang@intel.com> In-Reply-To: <1476338840-50003-2-git-send-email-qiming.yang@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzBmYzNhYTgtNTBkOS00ZjcxLTljM2UtNzVkYWVhYjA1YTA3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlBNSEpKc2Z6UGxiY2ttWTl4eEU4cFpEblJaaTQ0NURjZytSZUZzOFZSXC9ZPSJ9 x-ctpclassification: CTP_IC 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 2/2] net/i40e: fix VF bonded device link down X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Oct 2016 09:50:46 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qiming Yang > Sent: Thursday, October 13, 2016 2:07 PM > To: dev@dpdk.org > Cc: Yang, Qiming > Subject: [dpdk-dev] [PATCH 2/2] net/i40e: fix VF bonded device link down >=20 > Originally, using DPDK as host driver, when VF bonded device > uses I40E_VIRTCHNL_OP_GET_LINK_STAT to query PF the link status, If VF device is used as slave of a bond device, it will be polled periodica= lly though alarm. Interrupt is involved here. And then VF will send I40E_VIRTCHNL_OP_GET_LINK_STAT message to PF to get t= he status. The response is handled by interrupt callback. Interrupt is invo= lved here again. That's what bond device cannot bring up. > This patch uses PF to notify link status instead of VF query. This patch changes like that remove I40E_VIRTCHNL_OP_GET_LINK_STAT message,= link status in VF driver is updated when PF driver notify it, and VF store= s the links status locally. VF driver just returns the local status when be= ing required. > Fixes: 5c9222058df7 ("i40e: move to drivers/net/") The same comments as your previous patch. It is not exact commit introduced= this issue. Thanks Jingjing