From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: Yang Ming <ming.1.yang@nokia-sbell.com>
Cc: Moses Young <mosesyyoung@gmail.com>,
"dev@dpdk.org" <dev@dpdk.org>, "Bing Zhao" <bingz@nvidia.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"julien.meunier@nokia.com" <julien.meunier@nokia.com>,
Maayan Kashani <mkashani@nvidia.com>
Subject: Re: [PATCH v2 2/2] net/mlx5: enhance log file path
Date: Thu, 26 Jun 2025 15:06:48 +0200 [thread overview]
Message-ID: <20250626130637.c4a5jtfoglb3ssha@ds-vm-debian.local> (raw)
In-Reply-To: <PH7PR12MB701812C6D5EBD32CCB17D1D0B26CA@PH7PR12MB7018.namprd12.prod.outlook.com>
Hi Yang,
This patch breaks compilation on Windows:
https://lab.dpdk.org/results/dashboard/testruns/logs/1600918/
The problem is that mlx5_rxtx.c is used on both Linux and Windows.
Would you be able to fix the patch?
I suggest to do the following:
- Declare a function mlx5_os_debug_dump_file_open() in mlx5.h.
- Define it in drivers/net/mlx5/linux/mlx5_os.c.
Here the existing logic from the patch can be used to open the file.
- Define it in drivers/net/mlx5/windows/mlx5_os.c.
Here we can rely on rte_eal_get_runtime_dir() only,
since MLX5_SYSTEM_LOG_DIR is not defined correctly to work
on Windows as well.
(see https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/access-waccess?view=msvc-170)
- Replace the opening of the file in mlx5_dump_debug_information()
with mlx5_os_debug_dump_file_open().
Best regards,
Dariusz Sosnowski
On Wed, Jun 04, 2025 at 06:54:05AM +0000, Maayan Kashani wrote:
> Hi, Yang,
> Thanks for contributing,
> There are some failing CI tests.
> Can you fix it?
> https://patches.dpdk.org/project/dpdk/patch/20250321132750.4237-2-ming.1.yang@nokia-sbell.com/
>
> Regards,
> Maayan Kashani
>
> > -----Original Message-----
> > From: Moses Young <mosesyyoung@gmail.com>
> > Sent: Monday, 12 May 2025 13:13
> > To: Yang Ming <ming.1.yang@nokia-sbell.com>; dev@dpdk.org
> > Cc: Bing Zhao <bingz@nvidia.com>; Dariusz Sosnowski
> > <dsosnowski@nvidia.com>; stephen@networkplumber.org;
> > julien.meunier@nokia.com
> > Subject: Re: [PATCH v2 2/2] net/mlx5: enhance log file path
> >
> > External email: Use caution opening links or attachments
> >
> >
> > > Hi Experts,
> > >
> > > is there any chance to review and accept this patch?
> > >
> > > Brs,
> > >
> > > Yang Ming
> > >
next prev parent reply other threads:[~2025-06-26 13:07 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 socket " 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 [this message]
2025-06-26 12:48 ` [PATCH v2 1/2] net/mlx5: enhance socket " Dariusz Sosnowski
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=20250626130637.c4a5jtfoglb3ssha@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=mkashani@nvidia.com \
--cc=mosesyyoung@gmail.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).