DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Balaji K N <balaji.k.n@ericsson.com>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] long initialization time for EAL init
Date: Wed, 29 Jul 2020 12:02:37 +0200	[thread overview]
Message-ID: <CAJFAV8w-Ngy=QapmQOfkBbKP6-M4RK2Y2+GMN0nr_OpH24X43A@mail.gmail.com> (raw)
In-Reply-To: <VI1PR07MB6445755EE3F379FA53BCA9CEA1700@VI1PR07MB6445.eurprd07.prod.outlook.com>

On Wed, Jul 29, 2020 at 11:56 AM Balaji K N <balaji.k.n@ericsson.com> wrote:
>
> Hello,
>
> I tried by disabling mlockall and not do see long time for EAL init and is done quickly. Thanks for help.
>
> ovs-vswitchd unix:/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err -vfile:info --no-chdir --log-file=/var/log/openvswitch/ovs-vswitchd.log --pidfile=/var/run/openvswitch/ovs-vswitchd.pid --detach

Ok, just keep in mind that pages from the process are likely not
prefaulted and you could get random packet drops at the start of
packet handling.
You _might_ also get pages swapped out during the life of the process,
and again random packet drops.

We tried to enhance the DPDK init in this regard as Anatoly
mentionned, but this is not backported to 18.11 atm.


-- 
David Marchand


  reply	other threads:[~2020-07-29 10:02 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
2020-07-29  9:56     ` Balaji K N
2020-07-29 10:02       ` David Marchand [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to='CAJFAV8w-Ngy=QapmQOfkBbKP6-M4RK2Y2+GMN0nr_OpH24X43A@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=balaji.k.n@ericsson.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).