From: Zhihong Wang <zhihong.wang@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] Reduce DPDK initialization time
Date: Sun, 22 Nov 2015 14:13:33 -0500 [thread overview]
Message-ID: <1448219615-63746-1-git-send-email-zhihong.wang@intel.com> (raw)
This 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/
--------------
Changes in v1:
1. Use macro in sleep time initialization
2. Update commit message according to code change
--------------
Changes in RFC v2:
1. Use MAP_POPULATE flag to populate page tables
2. Add comments to avoid future misunderstanding
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 | 20 ++++++--------------
lib/librte_eal/linuxapp/eal/eal_timer.c | 2 +-
2 files changed, 7 insertions(+), 15 deletions(-)
--
2.5.0
next reply other threads:[~2015-11-23 2:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 19:13 Zhihong Wang [this message]
2015-11-22 19:13 ` [dpdk-dev] [PATCH 1/2] lib/librte_eal: Reduce timer " Zhihong Wang
2015-11-22 19:13 ` [dpdk-dev] [PATCH 2/2] lib/librte_eal: Remove unnecessary hugepage zero-filling Zhihong Wang
2015-11-23 2:28 ` Stephen Hemminger
2015-11-24 21:13 ` Thomas Monjalon
2015-11-24 22:44 ` Stephen Hemminger
2015-11-24 23:04 ` Thomas Monjalon
2015-11-25 1:57 ` Yuanhan Liu
2015-11-25 1:59 ` Wang, Zhihong
2016-01-21 14:59 ` [dpdk-dev] [PATCH 0/2] Reduce DPDK initialization time Thomas Monjalon
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=1448219615-63746-1-git-send-email-zhihong.wang@intel.com \
--to=zhihong.wang@intel.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).