From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 9D8CA1B4EF for ; Thu, 13 Dec 2018 12:36:49 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Dec 2018 03:36:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,348,1539673200"; d="scan'208";a="259161206" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.237.220.93]) ([10.237.220.93]) by orsmga004.jf.intel.com with ESMTP; 13 Dec 2018 03:36:46 -0800 To: Tiwei Bie Cc: dev@dpdk.org, John McNamara , Marko Kovacevic , przemyslawx.lal@intel.com, kuralamudhan.ramakrishnan@intel.com, ivan.coughlan@intel.com, ray.kinsella@intel.com, maxime.coquelin@redhat.com References: <28e25797ef95a0a74fd264388ab63b9cd980c265.1544546363.git.anatoly.burakov@intel.com> <20181213045904.GB26505@dpdk-tbie.sh.intel.com> From: "Burakov, Anatoly" Message-ID: <0d881c98-67a3-a95a-3a7e-750d0ac4130e@intel.com> Date: Thu, 13 Dec 2018 11:36:45 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 MIME-Version: 1.0 In-Reply-To: <20181213045904.GB26505@dpdk-tbie.sh.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v2 4/5] mem: use memfd for no-huge mode 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, 13 Dec 2018 11:36:50 -0000 On 13-Dec-18 4:59 AM, Tiwei Bie wrote: > On Tue, Dec 11, 2018 at 04:43:31PM +0000, Anatoly Burakov wrote: >> When running in no-huge mode, we anonymously allocate our memory. >> While this works for regular NICs and vdev's, it's not suitable >> for memory sharing scenarios such as virtio with vhost_user >> backend. >> >> To fix this, allocate no-huge memory using memfd, and register >> it with memalloc just like any other memseg fd. This will enable >> using rte_memseg_get_fd() API with --no-huge EAL flag. >> >> Signed-off-by: Anatoly Burakov >> --- >> >> Notes: >> v2: >> - Detect memfd support at compile time >> - Change memfd-related log level to debug >> >> doc/guides/rel_notes/release_19_02.rst | 5 +++ >> lib/librte_eal/linuxapp/eal/eal_memory.c | 54 +++++++++++++++++++++++- >> 2 files changed, 57 insertions(+), 2 deletions(-) >> >> diff --git a/doc/guides/rel_notes/release_19_02.rst b/doc/guides/rel_notes/release_19_02.rst >> index 960098582..420d51b5b 100644 >> --- a/doc/guides/rel_notes/release_19_02.rst >> +++ b/doc/guides/rel_notes/release_19_02.rst >> @@ -23,6 +23,11 @@ DPDK Release 19.02 >> New Features >> ------------ >> >> +* **Support for using VirtIO without hugepages** >> + >> + The --no-huge mode was augmented to use memfd-backed memory (on systems that >> + support memfd), to allow using VirtIO-based NICs without hugepages. > > It would be better to say virtio-user here, because virtio NICs > e.g. the one emulated by QEMU, could be something quite different. Thanks, will fix! > >> + >> .. This section should contain new features added in this release. >> Sample format: >> > [...] > -- Thanks, Anatoly