From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 825385588; Fri, 13 Jan 2017 03:04:54 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga104.jf.intel.com with ESMTP; 12 Jan 2017 18:04:53 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,220,1477983600"; d="scan'208";a="921969998" Received: from sjgaffne-mobl.ger.corp.intel.com (HELO [10.252.3.223]) ([10.252.3.223]) by orsmga003.jf.intel.com with ESMTP; 12 Jan 2017 18:04:50 -0800 To: "Tan, Jianfeng" , Alejandro Lucero References: <3355891.l3I590SjcV@polaris> <608e7dfd-5226-3e30-f43b-0fbe01aee16a@intel.com> Cc: Gregory Etelson , dev , "users@dpdk.org" From: Ferruh Yigit Message-ID: <7605618f-dc86-3060-473e-aff5545cac72@intel.com> Date: Fri, 13 Jan 2017 02:04:49 +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: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-users] [dpdk-dev] IGB_UIO: PCI Resources Management X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jan 2017 02:04:55 -0000 On 1/13/2017 1:51 AM, Tan, Jianfeng wrote: > > >> -----Original Message----- >> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Ferruh Yigit >> Sent: Thursday, January 12, 2017 8:22 PM >> To: Alejandro Lucero >> Cc: Gregory Etelson; dev; users@dpdk.org >> Subject: Re: [dpdk-users] [dpdk-dev] IGB_UIO: PCI Resources Management >> >> On 1/12/2017 12:12 PM, Alejandro Lucero wrote: >>> >>> >>> On Thu, Jan 12, 2017 at 11:55 AM, Ferruh Yigit >> > wrote: >>> >>> 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. >>> >>> >>> This is a known problem, but it is not just a UIO problem, and this >>> patch does not solve it, maybe it just solves part of it. >>> >>> In fact, a DPDK program crashing could imply the NIC DMAing after that >>> and after that memory was assigned to another program. >> >> Yes. >> Can there be a way to stop NIC DMA, (or prevent it access to mem >> anymore) when app crashes? >> I think that is what this patch is looking for. > > If I understand it correctly, you are looking for this patch? > http://dpdk.org/dev/patchwork/patch/17495/ > That is good, thanks Jianfeng, I will check it. btw, patch's current state is rejected, which is by mistake, it seems I confused it with "iomem and ioport mapping" patch, sorry about it, I will update its status immediately.