From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com [209.85.192.179]) by dpdk.org (Postfix) with ESMTP id 9AE0A3DC for ; Thu, 15 Dec 2016 20:14:36 +0100 (CET) Received: by mail-pf0-f179.google.com with SMTP id i88so10050544pfk.2 for ; Thu, 15 Dec 2016 11:14:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Fje90TVdDnNmsDTa1OWTrfT1qMpe20nT64rg3XWwzwo=; b=E1htzofWcrC4+RGI3MGujhUmyqZ8s/Pk4SOWzylZ4u1haJ6rlr/84dUy4H9KqDM4dc nZPIjECHlQDwLXcOzkbDneZfbsxnLx7WbcVQSqwepXlz4fKV+HAUmS5pxhrl5d7hLlzM kh5Pex56mngj8Ey4QjfzpfkQJZ8kAlSn7Oca7GgaaRTFT6Wb+i/xhhojr43qOw34mqBp OQUA6lMyMhWFa3tB9IxmKp5NhxsAarq7h3MIhVNeDTCiWTCDfbcb4+QIT7QYJXAd2LtV fllB8kiUENV2bQRzY0US5OOooXwg0I0VYwKP9c0AIFqOtmXB9GcMjIY6VlathK0an9yZ xLiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Fje90TVdDnNmsDTa1OWTrfT1qMpe20nT64rg3XWwzwo=; b=Xm7DwL+aUkeYfGsSwCpd7t6PH9g/N/A324JMDucUdXf9HqRUEypi4DtYz1t7Gt844w LBsejnfI4uyDdUg0ArS8GwHYfBEdSFKC2PUpp2pr6SXCnL95mGGqKzqiffsvfFmwf/8P xz0c/q0HNnodMfohfLezU3ZOe9vqNIRnovS/41h0mssMXsby2STLMGgNgz4hjeoxc6SD EU4q5ufH7XJUXoLLpshFvn4LLgTdmbslVLoI/T68Sq82TR5k+TCNdn3KWPSCG9tRd6Gp 6zT/8G2Rh/RA2UOQoJczs1fAjLMrMYGwERRmbLmXLp8Gramo6RXOxRbq5wQXv5HwOucT feRQ== X-Gm-Message-State: AKaTC024GefDSeEmEKWLFYrQajftLl2JuLvhcueC9A1QwvibIa+H3DgxfgbK8RdVy+2paA== X-Received: by 10.99.204.81 with SMTP id q17mr4720009pgi.168.1481829275833; Thu, 15 Dec 2016 11:14:35 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id c71sm6336777pga.22.2016.12.15.11.14.35 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 15 Dec 2016 11:14:35 -0800 (PST) Date: Thu, 15 Dec 2016 11:14:27 -0800 From: Stephen Hemminger To: edgar helmut Cc: "Hu, Xuekun" , "Wiles, Keith" , "users@dpdk.org" Message-ID: <20161215111427.3e9e72a2@xeon-e3> In-Reply-To: References: <88A92D351643BA4CB23E30315517062662F3C939@SHSMSX103.ccr.corp.intel.com> <20161215091740.0d34defe@xeon-e3> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-users] Dpdk poor performance on virtual machine 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, 15 Dec 2016 19:14:37 -0000 On Thu, 15 Dec 2016 19:29:54 +0200 edgar helmut wrote: > Stephen, this is not the case, it relies on using the transparent hugepages > which looks like 2M hugepages size. > Why should be a problem to back 1G pages of the guest to 2M pages at the > host? > the transparent hugepages makes the deployment much more flexible. The IOMMU has a cache (like TLB) which has a limited number of slots. If using 2M pages then the IOMMU cache misses will cause a performance drop just like CPU cache misses. I think Intel had some slides back at IDF 2012 that showed the impact.