patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Khadem Ullah <14pwcse1224@uetpeshawar.edu.pk>
To: thomas@monjalon.net, andrew.rybchenko@oktetlabs.ru,
	ferruh.yigit@amd.com, dsosnowski@nvidia.com
Cc: dev@dpdk.org, rasland@nvidia.com, stable@dpdk.org,
	viacheslavo@nvidia.com, orika@nvidia.com, suanmingm@nvidia.com,
	matan@nvidia.com
Subject: Re: [PATCH] ethdev: add dev_private check for secondary process
Date: Tue, 22 Jul 2025 08:14:15 -0400	[thread overview]
Message-ID: <20250722121415.1357967-1-14pwcse1224@uetpeshawar.edu.pk> (raw)
In-Reply-To: <20250721140127.r6orvsqsox7ytlhb@ds-vm-debian.local>

Yes, I think this can be addressed at both the PMD and ethdev layers.  
To centralize the logic and avoid duplication across drivers, I’ve also submitted 
a patch at the ethdev layer that checks for `dev_private` accessibility 
in the secondary process context.

Please see the updated patch here:  
https://patches.dpdk.org/project/dpdk/patch/20250722115439.1353573-1-14pwcse1224@uetpeshawar.edu.pk/

Looking forward to your feedback.

Best Regards, 
Khadem Ullah

  reply	other threads:[~2025-07-22 12:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21  7:38 [PATCH] net/mlx5: fix crash when secondary queries dev info after primary exits Khadem Ullah
2025-07-21 10:58 ` Dariusz Sosnowski
2025-07-21 11:38   ` [PATCH] net/mlx5: fix crash when using meter in transfer flow Khadem Ullah
2025-07-21 11:46   ` [PATCH] net/mlx5: fix crash when secondary queries dev info after primary exits Ivan Malov
2025-07-21 11:59     ` Thomas Monjalon
2025-07-21 14:01       ` Dariusz Sosnowski
2025-07-22 12:14         ` Khadem Ullah [this message]
2025-07-22 16:26         ` Ivan Malov
2025-07-22 16:52           ` Khadem Ullah
2025-07-22 19:30       ` Khadem Ullah
2025-07-21 14:50   ` 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=20250722121415.1357967-1-14pwcse1224@uetpeshawar.edu.pk \
    --to=14pwcse1224@uetpeshawar.edu.pk \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=ferruh.yigit@amd.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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).