From: Damien Le Moal <dlemoal@kernel.org>
To: linux-nvme@lists.infradead.org, Keith Busch <kbusch@kernel.org>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: [PATCH v3 0/4] nvme pci-epf target and tcp host fixes
Date: Thu, 13 Feb 2025 15:52:27 +0900 [thread overview]
Message-ID: <20250213065231.598527-1-dlemoal@kernel.org> (raw)
All,
4 patches in this series to fix some issues with the PCI endpoint
function target driver and a trivial fix for a compilation warning with
the tcp fabrics host driver.
Changes from v2:
- Fixed a typo in the commit message of patch 3
- Added review tags from Christoph
Changes from v1:
- Added patch 3 to fixe RCU stalls under heavy workload with the
pci-epf target driver
Damien Le Moal (4):
nvmet: pci-epf: Correctly initialize CSTS when enabling the controller
nvmet: pci-epf: Do not uselessly write the CSTS register
nvmet: pci-epf: Avoid RCU stalls under heavy workload
nvme: tcp: Fix compilation warning with W=1
drivers/nvme/host/tcp.c | 2 +-
drivers/nvme/target/pci-epf.c | 39 ++++++++++++++++++++++++++---------
2 files changed, 30 insertions(+), 11 deletions(-)
--
2.48.1
next reply other threads:[~2025-02-13 6:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 6:52 Damien Le Moal [this message]
2025-02-13 6:52 ` [PATCH v3 1/4] nvmet: pci-epf: Correctly initialize CSTS when enabling the controller Damien Le Moal
2025-02-13 6:52 ` [PATCH v3 2/4] nvmet: pci-epf: Do not uselessly write the CSTS register Damien Le Moal
2025-02-13 6:52 ` [PATCH v3 3/4] nvmet: pci-epf: Avoid RCU stalls under heavy workload Damien Le Moal
2025-02-13 6:52 ` [PATCH v3 4/4] nvme: tcp: Fix compilation warning with W=1 Damien Le Moal
2025-02-17 7:50 ` [PATCH v3 0/4] nvme pci-epf target and tcp host fixes Sagi Grimberg
2025-02-18 15:45 ` Keith Busch
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=20250213065231.598527-1-dlemoal@kernel.org \
--to=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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.