From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id F1FE2A052B; Wed, 29 Jul 2020 10:53:08 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D23D0F04; Wed, 29 Jul 2020 10:53:08 +0200 (CEST) Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [216.205.24.74]) by dpdk.org (Postfix) with ESMTP id 6E100E07 for ; Wed, 29 Jul 2020 10:53:06 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1596012785; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=t4fZmhdtcjQEk49qPeccqnWEMe4y/m82GNf4ndAfuvk=; b=XXaHv1yTx7a2X7ghiVAv2SM4lu9WfdJUtObLB+voKk0r2XJuziFTmG+IF7CAOSeu6nyZDX DCwEJ/yRuUTtEfItJ0J2rSOT91XsgmL0B0pHSIS2gDcCIx38B/+bP1EvBKz82+QBPbFw67 x+diQCMYdfxI9xV+5H7Jw5AAmAR7K/c= Received: from mail-vk1-f200.google.com (mail-vk1-f200.google.com [209.85.221.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-499--dDW4my4NzS0ho8CdgfwHQ-1; Wed, 29 Jul 2020 04:53:04 -0400 X-MC-Unique: -dDW4my4NzS0ho8CdgfwHQ-1 Received: by mail-vk1-f200.google.com with SMTP id m2so4445757vke.1 for ; Wed, 29 Jul 2020 01:53:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=t4fZmhdtcjQEk49qPeccqnWEMe4y/m82GNf4ndAfuvk=; b=lQDbPVGLPEziPmM6Psa5cAgTKMN4SlIWglhtZSJNAYlNE1OSrOkFD1Xrg6AfKZ2nQr NqhQNz5NU/vQuzFiNLCaL0s0Cm38QTexiZ5+hxI5pGdaM2FxqY31qDfFEOgpOsMPknDj gLP9geJoVsAOTvCCZxUiw0n2u35SYuRQlJFPtsvw9e3ns3DvdN+HX0/520CzoCkyXqDx XVjx8bGTDbchrGJ7hP1TNrwDyDcFq3gRbMcbhh20V6a/pQYF9cbb/TAugy5qPGJ5fb2w M9Kkn3Sw91q7KgGv3svJCTxjUQuNyW8qEMlltB2P45Tn4t9n7Q4Pa/r4Vt/pzDZU9W8L 1lBQ== X-Gm-Message-State: AOAM533rS+HqxW1a2JGOqdo2WGBKkCdA5LbGKVrn+xW9rLmd4OpJmJKI 1kwYYotVdC1NzRuUf+ThMw/3h7C1bap0+W2svMDHMlaPmR1PjLjU0OKC+xE34vTpeAJ+emwFq9B eZ1PCqylJ9G4ZYs50S18= X-Received: by 2002:ab0:5a72:: with SMTP id m47mr22698907uad.86.1596012783815; Wed, 29 Jul 2020 01:53:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwwN3v4/tyv5WkLIgPiB6Dzt4jYNvFDZNGZDfSgzm2kVurc4OqVqfijAO0W96rnVz+v9UUGk5ncm5stNno5iPw= X-Received: by 2002:ab0:5a72:: with SMTP id m47mr22698897uad.86.1596012783452; Wed, 29 Jul 2020 01:53:03 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 29 Jul 2020 10:52:52 +0200 Message-ID: To: Balaji K N Cc: "dev@dpdk.org" X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] long initialization time for EAL init 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, Jul 29, 2020 at 10:51 AM Balaji K N wrote= : > We are using OVS 2.12.0 with DPDK 18.11.2 release on Ubuntu 16.04 LTS. W= e do observe long initialization time for EAL init ( ~10 seconds for EAL me= mory 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 (re= served during boot time). We are using only 2MB huge pages for OVS process. > NIC : Ethernet 10G 2P X520 ( ixgbe drive= r ) > > Passing below EAL arguments with OVS process. > 2020-07-23T09:46:58.878Z|00014|dpdk|INFO|EAL ARGS: ovs-vswitchd -w 0000:0= 4:00.0,support-multi-driver=3D1 -w 0000:42:00.0,support-multi-driver=3D1 -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_vir= tual_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? --=20 David Marchand