On Mon, 21 Jul 2025 12:58:19 +0200
Dariusz Sosnowski wrote:
> I don't think it's an issue on PMD level, but rather on
> ethdev/multi-process handling level.
>
> When primary process closes the port, ethdev library zeroes and frees
> device data shared between processes.
> ethdev port data (rte_e
On Mon, Jul 21, 2025 at 01:59:59PM +0200, Thomas Monjalon wrote:
> 21/07/2025 13:46, Ivan Malov:
> > On Mon, 21 Jul 2025, Dariusz Sosnowski wrote:
> >
> > > + mlx5 maintainers
> > >
> > > Thank you for the patch.
> > >
> > > Could you please include other PMD maintainers (or other maintainers,
>
21/07/2025 13:46, Ivan Malov:
> On Mon, 21 Jul 2025, Dariusz Sosnowski wrote:
>
> > + mlx5 maintainers
> >
> > Thank you for the patch.
> >
> > Could you please include other PMD maintainers (or other maintainers,
> > depending on changed code)
> > in the future patches?
> > There is a script whi
On Mon, 21 Jul 2025, Dariusz Sosnowski wrote:
+ mlx5 maintainers
Thank you for the patch.
Could you please include other PMD maintainers (or other maintainers, depending
on changed code)
in the future patches?
There is a script which automatically adds maintainers while sending a patch.
It is
+ mlx5 maintainers
Thank you for the patch.
Could you please include other PMD maintainers (or other maintainers, depending
on changed code)
in the future patches?
There is a script which automatically adds maintainers while sending a patch.
It is described in:
https://doc.dpdk.org/guides/contr
When the primary process exits, the shared mlx5 state becomes
unavailable to secondary processes. If a secondary process attempts
to query device information (e.g., via testpmd), a NULL dereference
may occur due to missing shared data.
This patch adds a check for shared context availability and fa
6 matches
Mail list logo
