From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id B26921B9F1 for ; Fri, 14 Dec 2018 11:06:09 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id E7EA85A1C4; Fri, 14 Dec 2018 10:06:08 +0000 (UTC) Received: from [10.36.112.58] (ovpn-112-58.ams2.redhat.com [10.36.112.58]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 79473600C1; Fri, 14 Dec 2018 10:06:05 +0000 (UTC) To: Anatoly Burakov , dev@dpdk.org Cc: John McNamara , Marko Kovacevic , przemyslawx.lal@intel.com, kuralamudhan.ramakrishnan@intel.com, ivan.coughlan@intel.com, tiwei.bie@intel.com, ray.kinsella@intel.com References: From: Maxime Coquelin Message-ID: <251a4847-b88b-87a2-e2e5-0a3ce8429f17@redhat.com> Date: Fri, 14 Dec 2018 11:06:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Fri, 14 Dec 2018 10:06:09 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH v3 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: Fri, 14 Dec 2018 10:06:09 -0000 On 12/13/18 12:43 PM, 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 > Acked-by: Tiwei Bie > --- > > Notes: > v3: > - Clarify release notes to state that the changes apply to > virtio-user NICs rather than virtio in general > > 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..f733ad139 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** > + With the title change you suggested: Reviewed-by: Maxime Coquelin Thanks, Maxime