DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	Balaji K N <balaji.k.n@ericsson.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] long initialization time for EAL init
Date: Wed, 29 Jul 2020 10:07:59 +0100
Message-ID: <27b57cde-a02a-a79c-b115-d173e09f0d79@intel.com> (raw)
In-Reply-To: <CAJFAV8yMWBUQLoS-cHEL8jdBz=DYBYRKFkt4z3HUzZvTNpJY0Q@mail.gmail.com>

On 29-Jul-20 9:52 AM, David Marchand wrote:
> On Wed, Jul 29, 2020 at 10:51 AM Balaji K N <balaji.k.n@ericsson.com> wrote:
>> We are using OVS 2.12.0  with DPDK 18.11.2 release on Ubuntu 16.04 LTS. We do observe long initialization time for EAL init ( ~10 seconds for EAL memory initialization).
>> Below is our hardware and memory configuration
>> Hardware                      : Dell Server
>> Sockets(NUMA)           : 2
>> CPUs                              : Each NUMA with 10 CPUs (Intel(R) Xeon(R) CPU E5-2660 v2 @ 2.20GHz)
>> RAM                              : 128 GB
>> Hugepages reserverd : 2048 huge pages of 2MB and 100 Huge pages of 1G (reserved during boot time). We are using only 2MB huge pages for OVS process.
>> NIC                                  : Ethernet 10G 2P X520 ( ixgbe driver )
>> Passing below EAL arguments with OVS process.
>> 2020-07-23T09:46:58.878Z|00014|dpdk|INFO|EAL ARGS: ovs-vswitchd -w 0000:04:00.0,support-multi-driver=1 -w 0000:42:00.0,support-multi-driver=1 -c 0x1 --huge-dir /mnt/huge_ovs_2M --socket-mem 2048,2048 --socket-limit 2048,2048.
>> We debugged further in DPDK and found out that mmap called in eal_get_virtual_area is taking more time ( rte_eal_init->  rte_eal_memory_init -> rte_eal_memseg_init -> memseg_primary_init -> alloc_va_space -> eal_get_virtual_area ->mmap ). Long initialization time is noticeable difference compared to prior release. Any pointers would be helpful.
> Did you try to start ovs with the --no-mlockall option?

That's most likely the culprit. I believe the recent mlock/MPROT changes 
are going to be backported to 18.11?


  reply	other threads:[~2020-07-29  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 15:56 Balaji K N
2020-07-29  8:52 ` David Marchand
2020-07-29  9:07   ` Burakov, Anatoly [this message]
2020-07-29  9:56     ` Balaji K N
2020-07-29 10:02       ` David Marchand
2020-07-28 17:58 Anil Kumar Koli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27b57cde-a02a-a79c-b115-d173e09f0d79@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=balaji.k.n@ericsson.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git