From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Manoj Vishwanathan <manojvishy@google.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<google-lan-reviews@googlegroups.com>
Subject: Re: [PATCH v1 0/5] IDPF Virtchnl fixes
Date: Thu, 15 Aug 2024 15:55:30 -0700 [thread overview]
Message-ID: <48a33292-7fae-74ba-e213-2fce437cdd4a@intel.com> (raw)
In-Reply-To: <20240813182747.1770032-1-manojvishy@google.com>
On 8/13/2024 11:27 AM, Manoj Vishwanathan wrote:
Hi Manoj,
It would be great if you could familiarize yourself with the netdev process:
https://docs.kernel.org/process/maintainer-netdev.html#netdev-faq
For the Intel drivers, we follow the same guidelines other than we use
iwl-net|iwl-next rather than net|net-next respectively.
> This patch series is to enhance IDPF virtchnl error reporting and some
> minor fixes to the locking sequence in virtchnl message handling
> we encountered while testing.
> Also includes a minor clean up with regards to warning we encountered
> in controlq section of IDPF.
The bug fixes should be broken out and designated for iwl-net and the
others to iwl-next. Fix patches should include a Fixes: tag.
Also, please use RCT for networking patches (patch 1).
Thanks,
Tony
> The issue we had here was a virtchnl processing delay leading to the
> "xn->salt" mismatch, transaction timeout and connection not recovering.
> This was due to default CPU bounded kworker workqueue for virtchnl message
> processing being starved by aggressive userspace load causing the
> virtchnl processing to be delayed and causing a transaction timeout.
> The reason the virtchnl process kworker was stalled as it
> was bound to CPU0 by default and there was immense IRQ traffic to CPU0.
> All of the above with an aggressive user space process on the same core
> lead to the change from Marco Leogrande to convert the idpf workqueues
> to unbound.
>
> Manoj Vishwanathan (3):
> idpf: address an rtnl lock splat in tx timeout recovery path
> idpf: Acquire the lock before accessing the xn->salt
> idpf: more info during virtchnl transaction time out
>
> Marco Leogrande (1):
> idpf: convert workqueues to unbound
>
> Willem de Bruijn (1):
> idpf: warn on possible ctlq overflow
>
> drivers/net/ethernet/intel/idpf/idpf_main.c | 15 ++++++++-----
> drivers/net/ethernet/intel/idpf/idpf_txrx.c | 14 ++++++++++++-
> .../net/ethernet/intel/idpf/idpf_virtchnl.c | 21 ++++++++++++++-----
> 3 files changed, 39 insertions(+), 11 deletions(-)
>
prev parent reply other threads:[~2024-08-15 22:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 18:27 [PATCH v1 0/5] IDPF Virtchnl fixes Manoj Vishwanathan
2024-08-13 18:27 ` [PATCH v1 1/5] idpf: address an rtnl lock splat in tx timeout recovery path Manoj Vishwanathan
2024-08-13 18:27 ` [PATCH v1 2/5] idpf: Acquire the lock before accessing the xn->salt Manoj Vishwanathan
2024-08-13 18:27 ` [PATCH v1 3/5] idpf: convert workqueues to unbound Manoj Vishwanathan
2024-08-13 18:27 ` [PATCH v1 4/5] idpf: more info during virtchnl transaction time out Manoj Vishwanathan
2024-08-13 19:28 ` [Intel-wired-lan] " Paul Menzel
2024-08-13 18:27 ` [PATCH v1 5/5] idpf: warn on possible ctlq overflow Manoj Vishwanathan
2024-08-13 19:19 ` Willem de Bruijn
2024-08-15 22:55 ` Tony Nguyen [this message]
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=48a33292-7fae-74ba-e213-2fce437cdd4a@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=google-lan-reviews@googlegroups.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manojvishy@google.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.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