DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, "Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] eal: create runtime dir even when shared data is not used
Date: Mon, 5 Jul 2021 16:11:54 +0200	[thread overview]
Message-ID: <CAJFAV8wyX0nkiWAUqx+3j6zFpiqBwMEH0m48st-3Sj1eOOL+dw@mail.gmail.com> (raw)
In-Reply-To: <20210702125554.606364-1-bruce.richardson@intel.com>

On Fri, Jul 2, 2021 at 2:56 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> When multi-process is not wanted and DPDK is run with the "no-shconf"
> flag, the telemetry library still needs a runtime directory to place the
> unix socket for telemetry connections. Therefore, rather than not
> creating the directory when this flag is set, we can change the code to
> attempt the creation anyway, but not error out if it fails. If it
> succeeds, then telemetry will be available, but if it fails, the rest of
> DPDK will run without telemetry. This ensures that the "in-memory" flag
> will allow DPDK to run even if the whole filesystem is read-only, for
> example.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> V2: add a warning for the no-shconf case, rather than skipping it silently.
>
>  lib/eal/linux/eal.c | 14 ++++++++------
>  1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/lib/eal/linux/eal.c b/lib/eal/linux/eal.c
> index ba19fc6347..ccb7535619 100644
> --- a/lib/eal/linux/eal.c
> +++ b/lib/eal/linux/eal.c
> @@ -838,12 +838,14 @@ eal_parse_args(int argc, char **argv)
>                 }
>         }
>
> -       /* create runtime data directory */
> -       if (internal_conf->no_shconf == 0 &&
> -                       eal_create_runtime_dir() < 0) {
> -               RTE_LOG(ERR, EAL, "Cannot create runtime directory\n");
> -               ret = -1;
> -               goto out;
> +       /* create runtime data directory. In no_shconf mode, skip any errors */
> +       if (eal_create_runtime_dir() < 0) {
> +               if (internal_conf->no_shconf == 0) {
> +                       RTE_LOG(ERR, EAL, "Cannot create runtime directory\n");
> +                       ret = -1;
> +                       goto out;
> +               } else
> +                       RTE_LOG(WARNING, EAL, "No DPDK runtime directory created\n");
>         }
>
>         if (eal_adjust_config(internal_conf) != 0) {
> --
> 2.30.2
>

Should this change be applied to FreeBSD too?

Reviewed-by: David Marchand <david.marchand@redhat.com>


-- 
David Marchand


  parent reply	other threads:[~2021-07-05 14:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01  9:34 [dpdk-dev] [PATCH] " Bruce Richardson
2021-07-01 14:43 ` Morten Brørup
2021-07-01 14:56   ` Bruce Richardson
2021-07-02 12:55 ` [dpdk-dev] [PATCH v2 1/2] " Bruce Richardson
2021-07-02 12:55   ` [dpdk-dev] [PATCH v2 2/2] telemetry: add extra log message on socket bind failure Bruce Richardson
2021-07-02 14:22     ` Morten Brørup
2021-07-05 10:16       ` Power, Ciara
2021-07-05 14:11     ` David Marchand
2021-07-02 14:21   ` [dpdk-dev] [PATCH v2 1/2] eal: create runtime dir even when shared data is not used Morten Brørup
2021-07-05 14:11   ` David Marchand [this message]
2021-07-05 14:39     ` Bruce Richardson
2021-07-07 12:35       ` David Marchand
2021-07-07 12:41         ` Bruce Richardson
2021-07-07 19:02   ` Tyler Retzlaff
2021-07-07 12:52 ` [dpdk-dev] [PATCH v3 " Bruce Richardson
2021-07-07 12:52   ` [dpdk-dev] [PATCH v3 2/2] telemetry: add extra log message on socket bind failure Bruce Richardson
2021-07-07 15:00   ` [dpdk-dev] [PATCH v3 1/2] eal: create runtime dir even when shared data is not used David Marchand

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=CAJFAV8wyX0nkiWAUqx+3j6zFpiqBwMEH0m48st-3Sj1eOOL+dw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=mb@smartsharesystems.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).