DPDK patches and discussions
 help / color / mirror / Atom feed
From: Moses Young <mosesyyoung@gmail.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3 1/2] net/mlx5: improve socket file path handling
Date: Wed, 26 Nov 2025 17:10:18 +0800	[thread overview]
Message-ID: <b6d3eabc-de9b-4709-b161-337a2bc9623e@gmail.com> (raw)
In-Reply-To: <20251118144559.hpcgungifxd2hv3l@ds-vm-debian.local>

[-- Attachment #1: Type: text/plain, Size: 806 bytes --]

Hi Dariusz, Stephen, and the team,

Thank you for the detailed update and for taking the time to discuss the 
series internally.

I fully understand the concerns regarding backward compatibility and the 
impact on external tooling. If moving the UNIX socket path from /var/tmp 
to a proper runtime directory requires a broader change across dependent 
tools, postponing it to the next release cycle makes sense.

I'm glad to hear that the issue has been acknowledged and that the team 
plans to address it in a more complete way in the upcoming cycle. I 
appreciate the consideration regarding attribution as well.

Please let me know if there is anything I can help with during the 
redesign or review phase.
Thanks again for the clarification and for handling this thoughtfully.

Best regards,
Yang Ming

[-- Attachment #2: Type: text/html, Size: 1187 bytes --]

  reply	other threads:[~2025-11-26  9:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-13  9:24 [PATCH 1/2] net/mlx5: improve socket file path 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-07-20  8:57             ` Moses Young
2025-06-26 12:48   ` [PATCH v2 1/2] net/mlx5: enhance socket " Dariusz Sosnowski
2025-08-29 14:49   ` [PATCH v3 1/2] net/mlx5: improve socket file path handling Yang Ming
2025-08-29 14:49     ` [PATCH v3 2/2] net/mlx5: improve debug dump " Yang Ming
2025-11-07 16:48       ` Dariusz Sosnowski
2025-11-17 17:56       ` Stephen Hemminger
2025-08-29 19:57     ` [PATCH v3 1/2] net/mlx5: improve socket " Stephen Hemminger
2025-08-31  0:55       ` Moses Young
2025-08-31  3:21         ` Stephen Hemminger
2025-09-01  1:40           ` Moses Young
2025-11-17 13:43     ` Raslan Darawsheh
2025-11-17 17:58     ` Stephen Hemminger
2025-11-18 14:45       ` Dariusz Sosnowski
2025-11-26  9:10         ` Moses Young [this message]
2025-11-08  1:16   ` [PATCH v2 1/2] net/mlx5: enhance socket file path Stephen Hemminger

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=b6d3eabc-de9b-4709-b161-337a2bc9623e@gmail.com \
    --to=mosesyyoung@gmail.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.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).