From: David Marchand <david.marchand@redhat.com>
To: "Van Haaren, Harry" <harry.van.haaren@intel.com>
Cc: Aaron Conole <aconole@redhat.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] service: stop lcore threads before 'finalize'
Date: Thu, 20 Feb 2020 14:25:29 +0100 [thread overview]
Message-ID: <CAJFAV8w9_m+TyzHsF76yXej2Y=YExnvLQZoow_cU6VnRMpDhLA@mail.gmail.com> (raw)
In-Reply-To: <MN2PR11MB4447E9C17B3505FFC271EBD7D7190@MN2PR11MB4447.namprd11.prod.outlook.com>
On Mon, Feb 10, 2020 at 3:16 PM Van Haaren, Harry
<harry.van.haaren@intel.com> wrote:
> > > We need a fix for this issue.
> >
> > +1
>
> > > Interestingly, Stephen patch that joins all pthreads at
> > > rte_eal_cleanup [1] makes this issue disappear.
> > > So my understanding is that we are missing a api (well, I could not
> > > find a way) to synchronously stop service lcores.
> >
> > Maybe we can take that patch as a fix. I hate to see this segfault
> > in the field. I need to figure out what I missed in my cleanup
> > (probably missed a synchronization point).
>
> I haven't easily reproduced this yet - so I'll investigate a way to
> reproduce with close to 100% rate, then we can identify the root cause
> and actually get a clean fix. If you have pointers to reproduce easily,
> please let me know.
>
ping.
I want a fix in 20.05, or I will start considering how to drop this thing.
--
David Marchand
next prev parent reply other threads:[~2020-02-20 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 19:50 Aaron Conole
2020-01-17 8:17 ` David Marchand
2020-02-04 13:34 ` David Marchand
2020-02-04 14:50 ` Aaron Conole
2020-02-10 14:16 ` Van Haaren, Harry
2020-02-10 14:42 ` David Marchand
2020-02-20 13:25 ` David Marchand [this message]
2020-02-21 12:28 ` Van Haaren, Harry
2020-03-10 13:04 ` David Marchand
2020-03-10 13:27 ` Van Haaren, Harry
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='CAJFAV8w9_m+TyzHsF76yXej2Y=YExnvLQZoow_cU6VnRMpDhLA@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@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).