From: David Marchand <david.marchand@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v6] eal: add function to check if primary proc alive
Date: Tue, 8 Mar 2016 12:19:56 +0100 [thread overview]
Message-ID: <CALwxeUuiPa9_fo-51x96RDcUfAhWE1EcPeEZAKE2QLmNtwTAJw@mail.gmail.com> (raw)
In-Reply-To: <2251445.Z6GIcehbaX@xps13>
On Tue, Mar 8, 2016 at 12:13 PM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> 2016-03-08 09:58, Van Haaren, Harry:
>> From: David Marchand [mailto:david.marchand@6wind.com]
>> > When I look at this new api, I am under the impression that you are
>> > supposed to check for primary liveliness once dpdk init has finished
>> > (from your secondary process point of view), not before and not while
>> > it is initialising.
>>
>> The issue is that if a secondary process is initialized, it holds a read
>> lock on /var/run/.rte_config and this prevents a primary from starting.
>
> The new function is advertised as a monitoring feature.
> But it seems to be also a workaround for an ordering issue when starting
> primary and secondary processes concurrently, right?
+1
--
David Marchand
next prev parent reply other threads:[~2016-03-08 11:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 13:25 [dpdk-dev] [PATCH] " Harry van Haaren
2016-01-21 6:14 ` Qiu, Michael
2016-01-21 6:19 ` Matthew Hall
2016-01-21 9:02 ` Van Haaren, Harry
2016-01-22 17:37 ` Bruce Richardson
2016-01-25 8:06 ` Qiu, Michael
2016-01-25 11:44 ` Van Haaren, Harry
2016-01-26 19:13 ` Bruce Richardson
2016-01-27 10:35 ` Van Haaren, Harry
2016-01-25 8:11 ` Qiu, Michael
2016-01-25 11:51 ` Van Haaren, Harry
2016-01-26 2:25 ` Qiu, Michael
2016-01-26 9:04 ` Van Haaren, Harry
2016-01-26 11:07 ` Qiu, Michael
2016-01-26 11:19 ` Van Haaren, Harry
2016-01-27 10:31 ` [dpdk-dev] [PATCH v2] " Harry van Haaren
2016-02-02 14:11 ` [dpdk-dev] [PATCH v3] " Harry van Haaren
2016-02-23 14:10 ` [dpdk-dev] [PATCH v4] " Harry van Haaren
2016-02-24 13:50 ` Tahhan, Maryam
2016-03-04 18:07 ` Thomas Monjalon
2016-03-07 11:37 ` [dpdk-dev] [PATCH v5] " Harry van Haaren
2016-03-07 12:02 ` [dpdk-dev] [PATCH v6] " Harry van Haaren
2016-03-08 8:42 ` David Marchand
2016-03-08 9:58 ` Van Haaren, Harry
2016-03-08 11:13 ` Thomas Monjalon
2016-03-08 11:19 ` David Marchand [this message]
2016-03-08 13:57 ` Van Haaren, Harry
2016-03-08 14:40 ` David Marchand
2016-03-08 17:07 ` [dpdk-dev] [PATCH v7 0/2] eal: add function to check primary alive Harry van Haaren
2016-03-08 17:07 ` [dpdk-dev] [PATCH v7 1/2] eal: fix race-condition in pri/sec proc startup Harry van Haaren
2016-03-08 17:07 ` [dpdk-dev] [PATCH v7 2/2] eal: add function to check if primary proc alive Harry van Haaren
2016-03-09 10:12 ` [dpdk-dev] [PATCH v8 0/2] eal: add function to check primary alive Harry van Haaren
2016-03-09 10:12 ` [dpdk-dev] [PATCH v8 1/2] eal: fix race-condition in pri/sec proc startup Harry van Haaren
2016-03-09 13:23 ` Sergio Gonzalez Monroy
2016-03-09 10:12 ` [dpdk-dev] [PATCH v8 2/2] eal: add function to check if primary proc alive Harry van Haaren
2016-03-09 11:07 ` [dpdk-dev] [PATCH v8 0/2] eal: add function to check primary alive David Marchand
2016-03-09 12:59 ` Sergio Gonzalez Monroy
2016-03-09 13:37 ` [dpdk-dev] [PATCH v9 " Harry van Haaren
2016-03-09 13:37 ` [dpdk-dev] [PATCH v9 1/2] eal: fix race-condition in pri/sec proc startup Harry van Haaren
2016-03-09 14:27 ` Sergio Gonzalez Monroy
2016-03-09 13:37 ` [dpdk-dev] [PATCH v9 2/2] eal: add function to check if primary proc alive Harry van Haaren
2016-03-09 15:02 ` Thomas Monjalon
2016-03-09 15:17 ` [dpdk-dev] [PATCH v9 0/2] eal: add function to check primary alive 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=CALwxeUuiPa9_fo-51x96RDcUfAhWE1EcPeEZAKE2QLmNtwTAJw@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).