From: Bruce Richardson <bruce.richardson@intel.com>
To: Jim Harris <james.r.harris@intel.com>
Cc: dev@dpdk.org, anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] timer: use rte_mp_msg to pass TSC hz to secondary procs
Date: Mon, 26 Aug 2019 10:54:57 +0100 [thread overview]
Message-ID: <20190826095457.GC1731@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <156586845525.44449.11798632267644345382.stgit@jrharri1-skx>
On Thu, Aug 15, 2019 at 04:27:35AM -0700, Jim Harris wrote:
> rte_eal_init() is much faster in secondary processes since
> hugepages don't need to be zeroed. But there's still
> non-trivial delays in the timer subsystem initialization
> due to the 100ms sleep used to calculate TSC hz. So use
> the rte_mp_msg framework to allow secondary processes
> to get the TSC hz from the primary process.
>
> This cuts rte_eal_init() execution time in a secondary
> process from 165ms to 66ms in my test program.
>
> Signed-off-by: Jim Harris <james.r.harris@intel.com>
> ---
Rather than messaging, can we not just move the CPU frequency to being
stored in a shared memory location? It's not something where different
processes are going to need to be provided with different values.
prev parent reply other threads:[~2019-08-26 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 11:27 Jim Harris
2019-08-15 11:27 ` [dpdk-dev] [PATCH 2/2] timer: don't check tsc flags in secondary processes Jim Harris
2019-08-16 7:56 ` [dpdk-dev] [PATCH 1/2] timer: use rte_mp_msg to pass TSC hz to secondary procs Burakov, Anatoly
2019-08-16 19:01 ` Harris, James R
2019-08-26 9:54 ` Bruce Richardson [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=20190826095457.GC1731@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=james.r.harris@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).