DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: detach interrupt and worker threads
Date: Wed, 29 Sep 2021 08:21:03 +0200	[thread overview]
Message-ID: <CAJFAV8yvOum3ru36238vbfOg9+1Cm7g-KoAydW-cAdC5GaofZg@mail.gmail.com> (raw)
In-Reply-To: <20210819024100.1710184-1-stephen@networkplumber.org>

On Thu, Aug 19, 2021 at 4:41 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> The EAL library does not wait (pthread_join) these threads
> so the should be detached so that library can release resources.
> This shows up when looking for memory leaks with tools like
> valgrind.

The FreeBSD interrupt thread can be detached too.

There is also the hpet-msb-inc thread in Linux that could be detached,
maybe in a followup patch?

>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>

With FreeBSD interrupt thread addition, you can add:
Reviewed-by: David Marchand <david.marchand@redhat.com>


-- 
David Marchand


      reply	other threads:[~2021-09-29  6:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19  2:41 Stephen Hemminger
2021-09-29  6:21 ` David Marchand [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=CAJFAV8yvOum3ru36238vbfOg9+1Cm7g-KoAydW-cAdC5GaofZg@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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
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).