From: Simon Horman <horms@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Madhu Chittim <madhu.chittim@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next] idpf: modify vport_cfg_lock to be per-vport
Date: Fri, 17 Jan 2025 09:19:04 +0000 [thread overview]
Message-ID: <20250117091904.GH6206@kernel.org> (raw)
In-Reply-To: <20250116135530.94562-1-ahmed.zaki@intel.com>
On Thu, Jan 16, 2025 at 06:55:30AM -0700, Ahmed Zaki wrote:
> The vport config lock protects the vports queues and config data. These
> mainly change in soft reset path. Since there is no dependency across
> vports, there is no need for this lock to be global.
>
> Move the lock to be per-vport and allow one vport to reset without
> locking the rest of the vports.
>
> Reviewed-by: Madhu Chittim <madhu.chittim@intel.com>
> Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>
> ---
> depends on iwl series:
> https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=431435
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Ahmed Zaki <ahmed.zaki@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
Madhu Chittim <madhu.chittim@intel.com>
Subject: Re: [PATCH iwl-next] idpf: modify vport_cfg_lock to be per-vport
Date: Fri, 17 Jan 2025 09:19:04 +0000 [thread overview]
Message-ID: <20250117091904.GH6206@kernel.org> (raw)
In-Reply-To: <20250116135530.94562-1-ahmed.zaki@intel.com>
On Thu, Jan 16, 2025 at 06:55:30AM -0700, Ahmed Zaki wrote:
> The vport config lock protects the vports queues and config data. These
> mainly change in soft reset path. Since there is no dependency across
> vports, there is no need for this lock to be global.
>
> Move the lock to be per-vport and allow one vport to reset without
> locking the rest of the vports.
>
> Reviewed-by: Madhu Chittim <madhu.chittim@intel.com>
> Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>
> ---
> depends on iwl series:
> https://patchwork.ozlabs.org/project/intel-wired-lan/list/?series=431435
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-01-17 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 13:55 [Intel-wired-lan] [PATCH iwl-next] idpf: modify vport_cfg_lock to be per-vport Ahmed Zaki
2025-01-16 13:55 ` Ahmed Zaki
2025-01-17 9:19 ` Simon Horman [this message]
2025-01-17 9:19 ` Simon Horman
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=20250117091904.GH6206@kernel.org \
--to=horms@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.