From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com [209.85.218.43]) by dpdk.org (Postfix) with ESMTP id 4E24B9190 for ; Thu, 26 Nov 2015 15:37:19 +0100 (CET) Received: by oiww189 with SMTP id w189so47902596oiw.3 for ; Thu, 26 Nov 2015 06:37:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=EN/VCMZLZwNGm9LwVaeKq7eS/0tl1SCVEebZQwtK6m4=; b=I3MxIgWwTqfn6Z2WBg44huONf23VcxxDaEekyvKXXChRWe62LuAGcLw4V22XVk6mp8 FfkhmItvEQOAsPB1E/Qu+UyJet4AK/IlNge7MvZ5B7l+BQH7hQAik8aszZOJQmnMJEsc sstMrDvd+gzuhL67Xd70n4UWvZY/l1EoKV0PgtrsddIeFS5K4ofSeE3Ux5pWZ0JC8fH8 wZwkv1xsWK/pCHXdptewALLsxyzOf2O5uL4ziu9sC4BYy+nhT4raOmLJQZ16e9ugPN5D oIO65ABmwfiLZz7kMuMxTKxrCEc4Gu26SAEJEldMWGrHGabkrWh9Zo1ft8DmI7+uKS+R 4TPw== MIME-Version: 1.0 X-Received: by 10.202.228.137 with SMTP id b131mr28658740oih.100.1448548638690; Thu, 26 Nov 2015 06:37:18 -0800 (PST) Received: by 10.76.0.105 with HTTP; Thu, 26 Nov 2015 06:37:18 -0800 (PST) In-Reply-To: <56568EC7.6010905@ndsl.kaist.edu> References: <56554B08.3040400@ndsl.kaist.edu> <49956413.am4JoMJyVU@xps13> <20151125120239.GA23268@bricha3-MOBL3> <5690109.niDVrFKdOE@xps13> <5655BB2C.4090806@intel.com> <2601191342CEEE43887BDE71AB97725836ACD0DB@irsmsx105.ger.corp.intel.com> <56568EC7.6010905@ndsl.kaist.edu> Date: Thu, 26 Nov 2015 09:37:18 -0500 Message-ID: From: Kyle Larose To: Younghwan Go Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org Subject: Re: [dpdk-dev] no hugepage with UIO poll-mode driver 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: Thu, 26 Nov 2015 14:37:19 -0000 On Wed, Nov 25, 2015 at 11:47 PM, Younghwan Go wrote= : > Hello, > > Thank you all for helping us understand on issues with no hugepage option= . > > As Konstantin mentioned at the end, I tried using VFIO module instead of = IGB > UIO module. I enabled all necessary parameters (IOMMU, virtualization, > vfio-pci, VFIO permission) and ran my code with no hugepage option. > > At first, it seemed to receive packets fine, but after a while, it stoppe= d > receiving packets. I could temporarily remove this issue by not calling > rte_eth_tx_burst(). Also, when I looked at the received packets, they all > contained 0s instead of actual data. In my experience, if there's all zeroes it's because the NIC didn't actually write any packet data. In my case, to prove that, I initialized the mbuf data to a well-known pattern, and saw that after packet reception, the mbuf data was still that pattern, not the data I actually sent in the packet. From my analysis, I concluded that the ixgbe NIC was failing to actually write the data to memory because the corresponding PCI transaction was failing. The PCI transaction failed because something was going wrong with how IOMMU was mapping my VM's guest physical address to the host's physical address, and how that interacted with the PCI tree. I don't know if that's what you're seeing. However, it may be that the physical address being given to the NIC for the mbuf is invalid, or cannot be properly mapped to a real physical address if you're using IOMMU. When this happens, can you check the pcie AER registers on the NIC, if they exist? Maybe they'll show that something happened. Thanks, Kyle > Was there anything that I missed in > running with VFIO? I'm curious if no hugepage with no hugepage option was > confirmed to run with VFIO. > > Thank you, > Younghwan > > 2015-11-25 =EC=98=A4=ED=9B=84 11:12=EC=97=90 Ananyev, Konstantin =EC=9D= =B4(=EA=B0=80) =EC=93=B4 =EA=B8=80: >