From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Yang Ming <ming.1.yang@nokia-sbell.com>
Cc: <dev@dpdk.org>, <bingz@nvidia.com>, <stephen@networkplumber.org>,
<julien.meunier@nokia.com>
Subject: Re: [PATCH v2 1/2] net/mlx5: enhance socket file path
Date: Thu, 26 Jun 2025 14:48:42 +0200 [thread overview]
Message-ID: <20250626124819.ualtqzoosiap5vt7@ds-vm-debian.local> (raw)
In-Reply-To: <20250321132750.4237-1-ming.1.yang@nokia-sbell.com>
On Fri, Mar 21, 2025 at 09:27:49PM +0800, Yang Ming wrote:
> The directory /var/tmp may not be writable in a container's
> read-only mode. To address this issue, use the DPDK runtime
> directory as an alternative when /var/tmp is not writable.
>
> Cc: bingz@nvidia.com
> Cc: dsosnowski@nvidia.com
> Cc: stephen@networkplumber.org
> Cc: julien.meunier@nokia.com
>
> Signed-off-by: Yang Ming <ming.1.yang@nokia-sbell.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Best regards,
Dariusz Sosnowski
prev parent reply other threads:[~2025-06-26 12:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 9:24 [PATCH 1/2] net/mlx5: improve " Yang Ming
2024-12-13 9:24 ` [PATCH 2/2] net/mlx5: improve log " Yang Ming
2025-03-04 6:23 ` Bing Zhao
2025-03-05 3:20 ` Yang Ming
2025-03-10 14:59 ` Stephen Hemminger
2025-03-12 2:32 ` [External] " Yang Ming
2025-03-17 16:05 ` Bing Zhao
2025-03-21 9:48 ` Ming 1. Yang (NSB)
2024-12-13 17:12 ` [PATCH 1/2] net/mlx5: improve socket " Stephen Hemminger
2024-12-13 17:16 ` Bruce Richardson
2025-01-03 2:51 ` Yang Ming
2025-03-12 2:55 ` Yang Ming
2025-03-14 11:48 ` Dariusz Sosnowski
2025-03-21 13:27 ` [PATCH v2 1/2] net/mlx5: enhance " Yang Ming
2025-03-21 13:27 ` [PATCH v2 2/2] net/mlx5: enhance log " Yang Ming
2025-04-10 7:53 ` Yang Ming
2025-05-12 10:12 ` Moses Young
2025-06-04 6:54 ` Maayan Kashani
2025-06-26 13:06 ` Dariusz Sosnowski
2025-06-26 12:48 ` Dariusz Sosnowski [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=20250626124819.ualtqzoosiap5vt7@ds-vm-debian.local \
--to=dsosnowski@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=julien.meunier@nokia.com \
--cc=ming.1.yang@nokia-sbell.com \
--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).