From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 816151102C for ; Thu, 30 Mar 2017 14:33:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490877183; x=1522413183; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=7QDyMeHATTpUNmNoJglqcZDogVnu/FrpzrPIsafBfzk=; b=FHcaX8dF5F8F0TkmSQXgDLyZIIKGMO6gD5a4e3FzP5NCeA2G0H/LonbX o6fcvTWClTgNZHkV42WTwNuPSeGHgQ==; Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Mar 2017 05:33:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,246,1486454400"; d="scan'208";a="1113631527" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga001.jf.intel.com with ESMTP; 30 Mar 2017 05:33:02 -0700 Received: from fmsmsx124.amr.corp.intel.com (10.18.125.39) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 30 Mar 2017 05:33:02 -0700 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by fmsmsx124.amr.corp.intel.com (10.18.125.39) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 30 Mar 2017 05:33:02 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.253]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.82]) with mapi id 14.03.0248.002; Thu, 30 Mar 2017 20:32:58 +0800 From: "Wu, Jingjing" To: "Zhao1, Wei" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v4 0/3] net/i40e: vf port reset Thread-Index: AQHSqUKua6AEqIQuj0mmqyR7a3oixKGtUKdQ Date: Thu, 30 Mar 2017 12:32:57 +0000 Message-ID: <9BB6961774997848B5B42BEC655768F810D1BB3E@SHSMSX103.ccr.corp.intel.com> References: <1490866456-52241-1-git-send-email-wei.zhao1@intel.com> In-Reply-To: <1490866456-52241-1-git-send-email-wei.zhao1@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 v4 0/3] net/i40e: vf port reset X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 12:33:04 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wei Zhao > Sent: Thursday, March 30, 2017 5:34 PM > To: dev@dpdk.org > Subject: [dpdk-dev] [PATCH v4 0/3] net/i40e: vf port reset >=20 > The patches mainly finish following functions: > 1) get pf reset vf comamand falg from interrupt server function. > 2) reset vf port from testpmd app using a command. > 3) sore and restore vf related parameters. >=20 > v2: > -change the order of patch in the set. > -add more details in patch comment to clarify that the rte and tespmd pa= tch can > also used in pf port reset. > -add rte_free for memory free after restore. > -change varible name of reset_number to reset_falg. > -fix patch check warning. >=20 > v3: > -fix error of author mail address >=20 > v4: > -fix typo error > -add rte_wmb() after change the reset_ports. >=20 > zhao wei (3): > app/testpmd: add port reset command into testpmd > lib/librte_ether: add support for port reset > net/i40e: implement device reset on port Acked-by Jingjing Wu It looks like you sent 2 V4? Could you suspend one of them in Patchwork?