From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from minas.ics.muni.cz (minas.ics.muni.cz [147.251.4.46]) by dpdk.org (Postfix) with ESMTP id 5F3191B8B5 for ; Thu, 21 Jun 2018 13:02:46 +0200 (CEST) Received: from [192.168.1.136] (ip-89-103-72-95.net.upcbroadband.cz [89.103.72.95]) (authenticated user=98998@is.muni.cz bits=0) by minas.ics.muni.cz (8.14.4/8.14.4/Debian-4+deb7u1) with ESMTP id w5LB2gFD021913 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 21 Jun 2018 13:02:44 +0200 To: "Avi Cohen (A)" , "Rosen, Rami" , "users@dpdk.org" References: <34c3f20b-dcbb-5a47-d8c0-6af6635bc41a@ics.muni.cz> <9B0331B6EBBD0E4684FBFAEDA55776F9672C6986@HASMSX110.ger.corp.intel.com> <5dde9d52-3662-72ae-04a6-b5ad3e122562@ics.muni.cz> <9B0331B6EBBD0E4684FBFAEDA55776F9672C7B30@HASMSX110.ger.corp.intel.com> <9B0331B6EBBD0E4684FBFAEDA55776F9672C7B86@HASMSX110.ger.corp.intel.com> <586d777c-063a-1e0e-a6a8-bdcae3360ed6@ics.muni.cz> <9B0331B6EBBD0E4684FBFAEDA55776F9672CBC5E@HASMSX110.ger.corp.intel.com> From: =?UTF-8?Q?Martin_Dra=c5=a1ar?= Message-ID: Date: Thu, 21 Jun 2018 13:02:34 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=iso-8859-2 Content-Language: cs Content-Transfer-Encoding: 8bit X-Muni-Envelope-From: drasar@ics.muni.cz X-Muni-Envelope-To: avi.cohen@huawei.com X-Muni-Spam-TestIP: 89.103.72.95 X-Muni-Local-Auth: yes X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.3.9 (minas.ics.muni.cz [147.251.4.35]); Thu, 21 Jun 2018 13:02:45 +0200 (CEST) X-Virus-Scanned: clamav-milter 0.99.4 at minas X-Virus-Status: Clean X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on minas.ics.muni.cz Subject: Re: [dpdk-users] DPDK 17.05 does not find X510 card 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: Thu, 21 Jun 2018 11:02:46 -0000 Dne 21.6.2018 v 7:58 Avi Cohen (A) napsal(a): > Look at this > https://stackoverflow.com/questions/8213671/mmap-operation-not-permitted Hello Avi, thank you for chiming in. Neither iomem runtime parameter or allowing mmap on 0 page helped me. As for the latter, DPDK correctly maps to PCI region, so that is not the problem. Looking at the mmap source, there are basically only two points that result in EPERM error. First one is related to incorrect flag combination (not a DPDK case) the second is related to the file descriptor of the resource being locked (should not be, but it is the only possibility). That lock may have to do something with Secure boot being on, as almost the same system without secure boot is working ok. I built a custom kernel with CONFIG_STRICT_DEVMEM turned off, but it's going to take me some time to hammer it into the system, mainly because I am leaving for a vacation today. But it would be great if anyone, who has experience running DPDK on secure booted systems, could share their experience. Cheers, Martin