From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id C6CB3D592; Thu, 12 Jan 2017 12:55:46 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga105.fm.intel.com with ESMTP; 12 Jan 2017 03:55:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,349,1477983600"; d="scan'208";a="29460289" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.38]) ([10.237.220.38]) by orsmga002.jf.intel.com with ESMTP; 12 Jan 2017 03:55:44 -0800 To: Gregory Etelson , dev@dpdk.org, users@dpdk.org References: <3355891.l3I590SjcV@polaris> From: Ferruh Yigit Message-ID: <608e7dfd-5226-3e30-f43b-0fbe01aee16a@intel.com> Date: Thu, 12 Jan 2017 11:55:44 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <3355891.l3I590SjcV@polaris> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [dpdk-users] IGB_UIO: PCI Resources Management 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, 12 Jan 2017 11:55:47 -0000 On 12/9/2016 8:54 AM, Gregory Etelson wrote: > Hello, > > IGB_UIO driver does not close port PCI activities after DPDK process exits. > DPDK API provides rte_eth_dev_close() to manage port PCI, > but it can be skipped if process receives SIGKILL signal I guess I understand the problem. > The patches below provide IGB_UIO release callback and IXGBEVF release function But adding ixgbe specific code into igb_uio may not be good idea. Can be anything done one upper layer, pci layer, generic to all drivers? > With the patches, each time DPDK process terminates, > UIO release callback will trigger port PCI close. > On the down side, patched IGB_UIO can be bound to a single adapter type > > Regards, > Gregory <...>