DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "humin (Q)" <humin29@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Zhouchang (Forest)" <forest.zhouchang@huawei.com>,
	 Xiedonghui <xiedonghui@huawei.com>,
	"liudongdong (C)" <liudongdong3@huawei.com>,
	lihuisong <lihuisong@huawei.com>,
	"Huwei (Xavier)" <huwei87@hisilicon.com>,
	 "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	 Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [dpdk-dev] [RFC]app/testpmd: time-consuming question of mlockall function execution
Date: Fri, 6 Mar 2020 18:49:27 +0100	[thread overview]
Message-ID: <CAJFAV8zZc3cG01Je9w+vPmBXhuzwzTo72E9RNj+Jdow2df5+5w@mail.gmail.com> (raw)
In-Reply-To: <c689b990c2fd48b9bdc630e4284631ad@huawei.com>

On Wed, Feb 26, 2020 at 4:59 AM humin (Q) <humin29@huawei.com> wrote:
> We have another question about your patch. It seems that mlockall() also takes about two seconds after using this patch(about 0.2 seconds before using this patch), if we use "always" option for transparent hugepage configration. Is this reasonable and acceptable?

Hard to tell what reasonable/acceptable mean.
I'd say "it depends" :-).


> If that is ok, when will the patch be uploaded to DPDK community?

I sent a RFC earlier, that makes testpmd only lock pages containing text.
Can you have a try and report your findings?


Thanks.

-- 
David Marchand


  reply	other threads:[~2020-03-06 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-24  6:35 humin (Q)
2020-02-24  8:48 ` David Marchand
2020-02-26  3:59   ` [dpdk-dev] 答复: " humin (Q)
2020-03-06 17:49     ` David Marchand [this message]
2020-03-10 15:28       ` [dpdk-dev] " David Marchand
2020-03-13  8:25         ` [dpdk-dev] 答复: " humin (Q)

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=CAJFAV8zZc3cG01Je9w+vPmBXhuzwzTo72E9RNj+Jdow2df5+5w@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=forest.zhouchang@huawei.com \
    --cc=humin29@huawei.com \
    --cc=huwei87@hisilicon.com \
    --cc=lihuisong@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=thomas@monjalon.net \
    --cc=xiedonghui@huawei.com \
    /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).