From: "Qiu, Michael" <michael.qiu@intel.com>
To: "Wang, Zhihong" <zhihong.wang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Mata, Jhoanna E" <jhoanna.e.mata@intel.com>
Subject: Re: [dpdk-dev] [RFC PATCH 0/2] Reduce DPDK initialization time
Date: Thu, 24 Dec 2015 08:34:12 +0000 [thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E6028622F002AE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1447817231-10510-1-git-send-email-zhihong.wang@intel.com>
On 11/18/2015 6:30 PM, Zhihong Wang wrote:
> This RFC patch aims to reduce DPDK initialization time, which is important in cases such as micro service.
>
> Changes are:
>
> 1. Reduce timer initialization time
>
> 2. Remove unnecessary hugepage zero-filling operations
>
> With this patch:
>
> 1. Timer initialization time can be reduced by 4/10 second
>
> 2. Memory initialization time can be reduced nearly by half
>
> The 2nd topic has been brought up before in this thread:
> http://dpdk.org/dev/patchwork/patch/4219/
>
> Zhihong Wang (2):
> lib/librte_eal: Reduce timer initialization time
> lib/librte_eal: Remove unnecessary hugepage zero-filling
>
> lib/librte_eal/linuxapp/eal/eal_memory.c | 5 +----
> lib/librte_eal/linuxapp/eal/eal_timer.c | 2 +-
> 2 files changed, 2 insertions(+), 5 deletions(-)
>
As I tested with 8192 hugepages(size 2M), one nic 82599 bind, using time
to get the seconds used:
with this patch:
echo quit | time ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x3 -n 4 -- -i
2.15 user
5.55 system
0:07.82 elapsed
Without patch:
echo quit | time ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x3 -n 4 -- -i
3.18 user
5.63 system
0:09.32 elapsed
1.5s saved, 16% improvement, I don't know if this is good enough, but
indeed save lots of time.
Thanks,
Michael
prev parent reply other threads:[~2015-12-24 8:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 3:27 Zhihong Wang
2015-11-18 3:27 ` [dpdk-dev] [RFC PATCH 1/2] lib/librte_eal: Reduce timer " Zhihong Wang
2015-11-18 3:27 ` [dpdk-dev] [RFC PATCH 2/2] lib/librte_eal: Remove unnecessary hugepage zero-filling Zhihong Wang
2015-11-18 10:39 ` Mcnamara, John
2015-11-18 10:44 ` Wang, Zhihong
2015-11-18 12:07 ` Xie, Huawei
2015-11-18 16:00 ` Stephen Hemminger
2015-11-18 16:13 ` Richardson, Bruce
2015-11-18 19:09 ` Stephen Hemminger
2015-11-19 2:15 ` Wang, Zhihong
2015-11-19 6:04 ` Xie, Huawei
2015-11-19 6:32 ` Wang, Zhihong
2015-11-19 9:18 ` Sergio Gonzalez Monroy
2015-11-23 2:54 ` Xie, Huawei
2015-11-23 10:18 ` Bruce Richardson
2015-11-20 12:15 ` Bruce Richardson
2015-11-19 3:54 ` Wang, Zhihong
2015-11-19 6:09 ` Xie, Huawei
2015-11-19 9:14 ` Sergio Gonzalez Monroy
2015-11-23 3:46 ` Xie, Huawei
2015-11-23 4:07 ` Stephen Hemminger
2015-11-23 5:05 ` Xie, Huawei
2015-11-23 6:52 ` Stephen Hemminger
2015-11-25 18:24 ` Xie, Huawei
2015-12-24 8:34 ` Qiu, Michael [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=533710CFB86FA344BFBF2D6802E6028622F002AE@SHSMSX101.ccr.corp.intel.com \
--to=michael.qiu@intel.com \
--cc=dev@dpdk.org \
--cc=jhoanna.e.mata@intel.com \
--cc=zhihong.wang@intel.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).