From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: jerry.lilijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] eal: decrease the memory init time with many hugepages setup
Date: Thu, 02 Apr 2015 14:55:53 +0200 [thread overview]
Message-ID: <2705739.59RNFm1sab@xps13> (raw)
In-Reply-To: <1427974230-8572-1-git-send-email-jerry.lilijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-02 19:30, jerry.lilijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org:
> From: Lilijun <jerry.lilijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
>
> In the function map_all_hugepages(), hugepage memory is truly allocated by
> memset(virtaddr, 0, hugepage_sz). Then it costs about 40s to finish the
> dpdk memory initialization when 40000 2M hugepages are setup in host os.
Yes it's something we should try to reduce.
> In fact we can only write one byte to finish the allocation.
Isn't it a security hole?
This article speaks about "prezeroing optimizations" in Linux kernel:
http://landley.net/writing/memory-faq.txt
next prev parent reply other threads:[~2015-04-02 12:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 11:30 [PATCH] eal: decrease the memory init time with many hugepages setup jerry.lilijun-hv44wF8Li93QT0dZR+AlfA
[not found] ` <1427974230-8572-1-git-send-email-jerry.lilijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-04-02 12:55 ` Thomas Monjalon [this message]
2015-04-02 13:41 ` Jay Rolette
[not found] ` <CADNuJVpPYTx5eJW9rLqp2GcoHN3AqHyrGs-H5GMjGd=8emicBg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-03 9:04 ` Gonzalez Monroy, Sergio
[not found] ` <551E57A6.9070405-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-04-03 9:14 ` Thomas Monjalon
2015-04-03 9:37 ` Lilijun
2015-04-03 12:00 ` Gonzalez Monroy, Sergio
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=2705739.59RNFm1sab@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=jerry.lilijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.