DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Tyler Retzlaff <roretzla@linux.microsoft.com>
Cc: dev@dpdk.org, thomas@monjalon.net, dmitry.kozliuk@gmail.com,
	 anatoly.burakov@intel.com
Subject: Re: [PATCH v5 2/6] eal: add thread lifetime management
Date: Wed, 1 Mar 2023 09:11:43 +0100	[thread overview]
Message-ID: <CAJFAV8wmEbrx3-oy98QPdGUYFmgdgdE2Ot=nfXjVg4ahL3oAXA@mail.gmail.com> (raw)
In-Reply-To: <1664989651-29303-3-git-send-email-roretzla@linux.microsoft.com>

Hello Tyler,

On Wed, Oct 5, 2022 at 7:07 PM Tyler Retzlaff
<roretzla@linux.microsoft.com> wrote:
> diff --git a/lib/eal/unix/rte_thread.c b/lib/eal/unix/rte_thread.c
> index 9126595..d4c1a7f 100644
> --- a/lib/eal/unix/rte_thread.c
> +++ b/lib/eal/unix/rte_thread.c
> @@ -16,6 +16,11 @@ struct eal_tls_key {
>         pthread_key_t thread_index;
>  };
>
> +struct thread_routine_ctx {
> +       rte_thread_func thread_func;
> +       void *routine_args;
> +};
> +
>  static int
>  thread_map_priority_to_os_value(enum rte_thread_priority eal_pri, int *os_pri,
>         int *pol)
> @@ -75,6 +80,136 @@ struct eal_tls_key {
>         return 0;
>  }
>
> +static void *
> +thread_func_wrapper(void *arg)
> +{
> +       struct thread_routine_ctx ctx = *(struct thread_routine_ctx *)arg;
> +
> +       free(arg);
> +
> +       return (void *)(uintptr_t)ctx.thread_func(ctx.routine_args);
> +}
> +
> +int
> +rte_thread_create(rte_thread_t *thread_id,
> +               const rte_thread_attr_t *thread_attr,
> +               rte_thread_func thread_func, void *args)
> +{
> +       int ret = 0;
> +       pthread_attr_t attr;
> +       pthread_attr_t *attrp = NULL;
> +       struct thread_routine_ctx *ctx;
> +       struct sched_param param = {
> +               .sched_priority = 0,
> +       };
> +       int policy = SCHED_OTHER;
> +
> +       ctx = calloc(1, sizeof(*ctx));
> +       if (ctx == NULL) {
> +               RTE_LOG(DEBUG, EAL, "Insufficient memory for thread context allocations\n");
> +               ret = ENOMEM;
> +               goto cleanup;
> +       }
> +       ctx->routine_args = args;
> +       ctx->thread_func = thread_func;
> +
> +       if (thread_attr != NULL) {
> +               ret = pthread_attr_init(&attr);
> +               if (ret != 0) {
> +                       RTE_LOG(DEBUG, EAL, "pthread_attr_init failed\n");
> +                       goto cleanup;
> +               }
> +
> +               attrp = &attr;
> +
> +               /*
> +                * Set the inherit scheduler parameter to explicit,
> +                * otherwise the priority attribute is ignored.
> +                */
> +               ret = pthread_attr_setinheritsched(attrp,
> +                               PTHREAD_EXPLICIT_SCHED);
> +               if (ret != 0) {
> +                       RTE_LOG(DEBUG, EAL, "pthread_attr_setinheritsched failed\n");
> +                       goto cleanup;
> +               }
> +
> +
> +               if (thread_attr->priority ==
> +                               RTE_THREAD_PRIORITY_REALTIME_CRITICAL) {
> +                       ret = ENOTSUP;
> +                       goto cleanup;
> +               }
> +               ret = thread_map_priority_to_os_value(thread_attr->priority,
> +                               &param.sched_priority, &policy);
> +               if (ret != 0)
> +                       goto cleanup;
> +
> +               ret = pthread_attr_setschedpolicy(attrp, policy);
> +               if (ret != 0) {
> +                       RTE_LOG(DEBUG, EAL, "pthread_attr_setschedpolicy failed\n");
> +                       goto cleanup;
> +               }
> +
> +               ret = pthread_attr_setschedparam(attrp, &param);
> +               if (ret != 0) {
> +                       RTE_LOG(DEBUG, EAL, "pthread_attr_setschedparam failed\n");
> +                       goto cleanup;
> +               }
> +       }
> +
> +       ret = pthread_create((pthread_t *)&thread_id->opaque_id, attrp,
> +               thread_func_wrapper, ctx);
> +       if (ret != 0) {
> +               RTE_LOG(DEBUG, EAL, "pthread_create failed\n");
> +               goto cleanup;
> +       }
> +
> +       if (thread_attr != NULL && CPU_COUNT(&thread_attr->cpuset) > 0) {
> +               ret = rte_thread_set_affinity_by_id(*thread_id,
> +                       &thread_attr->cpuset);
> +               if (ret != 0) {
> +                       RTE_LOG(DEBUG, EAL, "rte_thread_set_affinity_by_id failed\n");
> +                       goto cleanup;
> +               }
> +       }
> +
> +       ctx = NULL;
> +cleanup:
> +       free(ctx);
> +       if (attrp != NULL)
> +               pthread_attr_destroy(&attr);
> +
> +       return ret;
> +}

I am looking back at potential races in our code while reviewing the
ctrl thread creation fix, and I stopped at this patch.

What happens if rte_thread_set_affinity_by_id() fails?
A new thread got started, but I don't see it being terminated in the
cleanup phase.


In this same situation, we may have a small race for a double free on
ctx since thread_func_wrapper() may have already been called from the
new thread.


I have the same concerns with the windows implementation.


-- 
David Marchand


  reply	other threads:[~2023-03-01  8:11 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 13:58 [PATCH 0/6] add thread lifetime and attributes API Tyler Retzlaff
2022-06-09 13:58 ` [PATCH 1/6] eal: add thread attributes Tyler Retzlaff
2022-06-09 13:58 ` [PATCH 2/6] eal: add thread lifetime management Tyler Retzlaff
2022-06-09 13:58 ` [PATCH 3/6] eal: add basic rte thread ID equal API Tyler Retzlaff
2022-06-09 22:24   ` Konstantin Ananyev
2022-06-10 22:48     ` Tyler Retzlaff
2022-06-11 12:25       ` Konstantin Ananyev
2022-06-13 13:39         ` Tyler Retzlaff
2022-06-10  0:40   ` fengchengwen
2022-06-09 13:58 ` [PATCH 4/6] test/threads: add tests for thread lifetime API Tyler Retzlaff
2022-06-09 13:58 ` [PATCH 5/6] test/threads: add tests for thread attributes API Tyler Retzlaff
2022-06-09 13:58 ` [PATCH 6/6] test/threads: remove unit test use of pthread Tyler Retzlaff
2022-06-14 23:47 ` [PATCH v2 0/6] add thread lifetime and attributes API Tyler Retzlaff
2022-06-14 23:47   ` [PATCH v2 1/6] eal: add thread attributes Tyler Retzlaff
2022-06-14 23:47   ` [PATCH v2 2/6] eal: add thread lifetime management Tyler Retzlaff
2022-06-18 12:59     ` Dmitry Kozlyuk
2022-06-20 17:39       ` Tyler Retzlaff
2022-06-21 16:24       ` Tyler Retzlaff
2022-06-21 18:51       ` Tyler Retzlaff
2022-06-21 19:44         ` Dmitry Kozlyuk
2022-06-21 21:28           ` Tyler Retzlaff
2022-06-21 22:24             ` Dmitry Kozlyuk
2022-06-22 18:21               ` Tyler Retzlaff
2022-06-14 23:47   ` [PATCH v2 3/6] eal: add basic rte thread ID equal API Tyler Retzlaff
2022-06-20  8:34     ` Konstantin Ananyev
2022-06-14 23:47   ` [PATCH v2 4/6] test/threads: add tests for thread lifetime API Tyler Retzlaff
2022-06-14 23:47   ` [PATCH v2 5/6] test/threads: add tests for thread attributes API Tyler Retzlaff
2022-06-14 23:47   ` [PATCH v2 6/6] test/threads: remove unit test use of pthread Tyler Retzlaff
2022-06-22 20:26 ` [PATCH v3 0/6] add thread lifetime and attributes API Tyler Retzlaff
2022-06-22 20:26   ` [PATCH v3 1/6] eal: add thread attributes Tyler Retzlaff
2022-06-22 20:26   ` [PATCH v3 2/6] eal: add thread lifetime management Tyler Retzlaff
2022-06-22 20:26   ` [PATCH v3 3/6] eal: add basic rte thread ID equal API Tyler Retzlaff
2022-06-22 20:26   ` [PATCH v3 4/6] test/threads: add tests for thread lifetime API Tyler Retzlaff
2022-06-22 20:26   ` [PATCH v3 5/6] test/threads: add tests for thread attributes API Tyler Retzlaff
2022-06-22 20:26   ` [PATCH v3 6/6] test/threads: remove unit test use of pthread Tyler Retzlaff
2022-06-27 16:56 ` [PATCH v4 0/6] add thread lifetime and attributes API Tyler Retzlaff
2022-06-27 16:56   ` [PATCH v4 1/6] eal: add thread attributes Tyler Retzlaff
2022-06-27 16:56   ` [PATCH v4 2/6] eal: add thread lifetime management Tyler Retzlaff
2022-06-27 16:56   ` [PATCH v4 3/6] eal: add basic rte thread ID equal API Tyler Retzlaff
2022-06-27 16:56   ` [PATCH v4 4/6] test/threads: add tests for thread lifetime API Tyler Retzlaff
2022-06-27 16:56   ` [PATCH v4 5/6] test/threads: add tests for thread attributes API Tyler Retzlaff
2022-06-27 16:56   ` [PATCH v4 6/6] test/threads: remove unit test use of pthread Tyler Retzlaff
2022-07-31 21:16   ` [PATCH v4 0/6] add thread lifetime and attributes API Dmitry Kozlyuk
2022-09-21  8:15   ` David Marchand
2022-09-29  7:02     ` David Marchand
2022-10-05 16:11     ` Tyler Retzlaff
2022-10-05 16:34       ` Tyler Retzlaff
2022-10-06  6:52         ` David Marchand
2022-10-06 15:14           ` Tyler Retzlaff
2022-10-06 13:36         ` Thomas Monjalon
2022-10-06 15:10           ` Tyler Retzlaff
2022-10-06 15:14             ` Thomas Monjalon
2022-10-06 15:20               ` Tyler Retzlaff
2022-10-06 15:26                 ` David Marchand
2022-10-06 15:27                   ` Tyler Retzlaff
2022-10-05 17:07 ` [PATCH v5 " Tyler Retzlaff
2022-10-05 17:07   ` [PATCH v5 1/6] eal: add thread attributes Tyler Retzlaff
2022-10-06  8:32     ` David Marchand
2022-10-05 17:07   ` [PATCH v5 2/6] eal: add thread lifetime management Tyler Retzlaff
2023-03-01  8:11     ` David Marchand [this message]
2023-03-01 20:34       ` Tyler Retzlaff
2022-10-05 17:07   ` [PATCH v5 3/6] eal: add basic rte thread ID equal API Tyler Retzlaff
2022-10-05 17:07   ` [PATCH v5 4/6] test/threads: add tests for thread lifetime API Tyler Retzlaff
2022-10-06  8:32     ` David Marchand
2022-10-06 15:19       ` Tyler Retzlaff
2022-10-05 17:07   ` [PATCH v5 5/6] test/threads: add tests for thread attributes API Tyler Retzlaff
2022-10-05 17:07   ` [PATCH v5 6/6] test/threads: remove unit test use of pthread Tyler Retzlaff
2022-10-06 19:25   ` [PATCH v5 0/6] add thread lifetime and attributes API David Marchand
2022-10-07 19:20     ` Tyler Retzlaff

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='CAJFAV8wmEbrx3-oy98QPdGUYFmgdgdE2Ot=nfXjVg4ahL3oAXA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=thomas@monjalon.net \
    /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).