From: Thomas Monjalon <thomas@monjalon.net>
To: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Cc: anatoly.burakov@intel.com, rsanford@akamai.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] timer: allow first subsystem init from secondary
Date: Thu, 09 May 2019 21:51:34 +0200 [thread overview]
Message-ID: <7268235.EfLeTirqVG@xps> (raw)
Message-ID: <20190509195134.vyOBtgwZZK550_f_karikVXOyTUFiTrsntEIZK7_1aM@z> (raw)
In-Reply-To: <1557430776-16355-1-git-send-email-erik.g.carrillo@intel.com>
09/05/2019 21:39, Erik Gabriel Carrillo:
> Since memzones can be reserved from secondary processes as well as
> primary processes, if the first call to the timer subsystem init
> function occurs in a secondary process, we should allow it to succeed.
>
> Fixes: c0749f7096c7 ("timer: allow management in shared memory")
>
> Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
I think this patch is too big for -rc4.
And it doesn't look so critical.
Do you agree to wait 19.08?
next prev parent reply other threads:[~2019-05-09 19:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 22:17 [dpdk-dev] [PATCH] " Erik Gabriel Carrillo
2019-05-08 22:17 ` Erik Gabriel Carrillo
2019-05-09 11:44 ` Burakov, Anatoly
2019-05-09 11:44 ` Burakov, Anatoly
2019-05-09 19:47 ` Carrillo, Erik G
2019-05-09 19:47 ` Carrillo, Erik G
2019-05-09 19:39 ` [dpdk-dev] [PATCH v2] " Erik Gabriel Carrillo
2019-05-09 19:39 ` Erik Gabriel Carrillo
2019-05-09 19:51 ` Thomas Monjalon [this message]
2019-05-09 19:51 ` Thomas Monjalon
2019-05-09 20:08 ` Carrillo, Erik G
2019-05-09 20:12 ` Thomas Monjalon
2019-05-09 20:12 ` Thomas Monjalon
2019-05-09 21:19 ` Carrillo, Erik G
2019-05-09 21:19 ` Carrillo, Erik G
2019-05-09 22:07 ` Thomas Monjalon
2019-05-09 22:07 ` 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=7268235.EfLeTirqVG@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=rsanford@akamai.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).