From: Thomas Monjalon <firstname.lastname@example.org> To: Anatoly Burakov <email@example.com> Cc: firstname.lastname@example.org, Bruce Richardson <email@example.com>, firstname.lastname@example.org, email@example.com Subject: Re: [dpdk-dev] [PATCH v4] eal: fix proc type auto detection Date: Tue, 30 Jul 2019 10:13:53 +0200 Message-ID: <3981792.lQiNHBRo4J@xps> (raw) In-Reply-To: <firstname.lastname@example.org> 24/07/2019 18:07, Anatoly Burakov: > Currently, primary process holds an exclusive lock on the config > file, thereby preventing other primaries from spinning up. However, > when the primary dies, the lock is no longer being held, even though > there might be other secondary processes still running. > > The fix is two-fold. First of all, downgrade the primary process's > exclusive lock to a shared lock once we have it. Second of all, > also take out shared locks on the config from the secondaries. We > are using fcntl() locks, which get dropped when the file handle is > closed, so also remove the closure of config file handle. > > Fixes: af75078fece3 ("first public release") > Cc: email@example.com > > Signed-off-by: Anatoly Burakov <firstname.lastname@example.org> This is not a new bug, and the fix is a bit complex, so it is deferred to 19.11 cycle. OK?
next prev parent reply index Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-23 13:19 [dpdk-dev] [PATCH] " Anatoly Burakov 2019-07-23 18:38 ` Stephen Hemminger 2019-07-24 10:04 ` [dpdk-dev] [PATCH v2] " Anatoly Burakov 2019-07-24 16:04 ` [dpdk-dev] [PATCH v3] " Anatoly Burakov 2019-07-24 16:07 ` [dpdk-dev] [PATCH v4] " Anatoly Burakov 2019-07-30 8:13 ` Thomas Monjalon [this message] 2019-07-30 9:19 ` Burakov, Anatoly 2019-08-12 10:03 ` David Marchand 2019-08-12 10:21 ` Van Haaren, Harry 2019-08-12 13:30 ` Burakov, Anatoly 2019-08-12 13:31 ` Burakov, Anatoly
Reply instructions: You may reply publically 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=3981792.lQiNHBRo4J@xps \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.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
DPDK-dev Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \ email@example.com firstname.lastname@example.org public-inbox-index dpdk-dev Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/ public-inbox