DPDK patches and discussions
 help / color / mirror / Atom feed
From: "humin (Q)" <humin29@huawei.com>
To: David Marchand <david.marchand@redhat.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: [dpdk-dev] 答复: [RFC]app/testpmd: time-consuming question of mlockall function execution
Date: Fri, 13 Mar 2020 08:25:07 +0000	[thread overview]
Message-ID: <8fd34743eb2d457fb284df5c029f71c2@huawei.com> (raw)
In-Reply-To: <CAJFAV8zLPeOZT6QjsFhzWKFWdmKZJFpJ6ANK5g3jpTpWTFFMnQ@mail.gmail.com>

Hello, this is my report about my findings: 

mlockall() takes a very short time for different transparent hugepage configurations after using the fix in EAL. Log as follows:

****** transparent_hugepage is madvise*******
[root@X6000-C23-3U dpdk-19.11]# strace -T -e trace=mlockall ./build/app/testpmd -l 0-1 -n 4 -w 0000:7d:01.0 --file-prefix=rte_lee --log-level=6 -- -i --rxq=1 --txq=1 --rxd=1024 --rxd=1024
EAL: No available hugepages reported in hugepages-2048kB
EAL: No available hugepages reported in hugepages-32768kB
EAL: No available hugepages reported in hugepages-64kB
EAL: VFIO support initialized
EAL:   using IOMMU type 1 (Type 1)
Interactive-mode selected
mlockall(MCL_CURRENT|MCL_FUTURE)        = 0 <0.014386>

Warning! port-topology=paired and odd forward ports number, the last port will pair with itself.

Configuring Port 0 (socket 0)
Port 0: 82:33:17:B1:43:57
Checking link statuses...
Done
Error during enabling promiscuous mode for port 0: Operation not supported - ignore
testpmd>
testpmd>
testpmd> quit

Stopping port 0...
Stopping ports...
Done

Shutting down port 0...
Closing ports...
0000:7d:01.0 hns3vf_dev_close(): Close port 0 finished
Done

Bye...
+++ exited with 0 +++

****** transparent_hugepage is never*******
[root@X6000-C23-3U dpdk-19.11]# strace -T -e trace=mlockall ./build/app/testpmd -l 0-8 -n 4 -w 0000:7d:01.0 --file-prefix=rte_lee --log-level=6 -- -i --rxq=8 --txq=8
EAL: No available hugepages reported in hugepages-2048kB
EAL: No available hugepages reported in hugepages-32768kB
EAL: No available hugepages reported in hugepages-64kB
EAL: VFIO support initialized
EAL:   using IOMMU type 1 (Type 1)
Interactive-mode selected
mlockall(MCL_CURRENT|MCL_FUTURE)        = 0 <0.031902>

Warning! port-topology=paired and odd forward ports number, the last port will pair with itself.

Configuring Port 0 (socket 0)
Port 0: 1E:46:8C:BC:7A:E7
Checking link statuses...
Done
Error during enabling promiscuous mode for port 0: Operation not supported - ignore
testpmd>
testpmd>
testpmd> quit

Stopping port 0...
Stopping ports...
Done

Shutting down port 0...
Closing ports...
0000:7d:01.0 hns3vf_dev_close(): Close port 0 finished
Done

Bye...
+++ exited with 0 +++


****** transparent_hugepage is always *******
[root@X6000-C23-3U dpdk-19.11]# strace -T -e trace=mlockall ./build/app/testpmd -l 0-8 -n 4 -w 0000:7d:01.0 --file-prefix=rte_lee --log-level=6 -- -i --rxq=8 --txq=8
EAL: No available hugepages reported in hugepages-2048kB
EAL: No available hugepages reported in hugepages-32768kB
EAL: No available hugepages reported in hugepages-64kB
EAL: VFIO support initialized
EAL:   using IOMMU type 1 (Type 1)
Interactive-mode selected
mlockall(MCL_CURRENT|MCL_FUTURE)        = 0 <0.017960>

Warning! port-topology=paired and odd forward ports number, the last port will pair with itself.

Configuring Port 0 (socket 0)
Port 0: EA:84:12:62:A5:98
Checking link statuses...
Done
Error during enabling promiscuous mode for port 0: Operation not supported - ignore
testpmd> quit

Stopping port 0...
Stopping ports...
Done

Shutting down port 0...
Closing ports...
0000:7d:01.0 hns3vf_dev_close(): Close port 0 finished
Done

Bye...
+++ exited with 0 +++















-----邮件原件-----
发件人: David Marchand [mailto:david.marchand@redhat.com] 
发送时间: 2020年3月10日 23:28
收件人: humin (Q) <humin29@huawei.com>
抄送: 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>
主题: Re: [RFC]app/testpmd: time-consuming question of mlockall function execution

On Fri, Mar 6, 2020 at 6:49 PM David Marchand <david.marchand@redhat.com> wrote:
>
> 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?

Let's forget about the change in testpmd.
I came with a different fix in EAL.
Can you have a try?

http://patchwork.dpdk.org/patch/66469/


-- 
David Marchand


      reply	other threads:[~2020-03-13  8:25 UTC|newest]

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

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=8fd34743eb2d457fb284df5c029f71c2@huawei.com \
    --to=humin29@huawei.com \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=forest.zhouchang@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).