From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/3] nvme-tcp: open-code nvme_tcp_queue_request() for R2T
Date: Tue, 22 Apr 2025 10:09:07 +0200 [thread overview]
Message-ID: <20250422080907.GA411@lst.de> (raw)
In-Reply-To: <20250403065522.90807-2-hare@kernel.org>
On Thu, Apr 03, 2025 at 08:55:20AM +0200, Hannes Reinecke wrote:
> When handling an R2T PDU we short-circuit nvme_tcp_queue_request()
> as we should not attempt to send consecutive PDUs. So open-code
> nvme_tcp_queue_request() for R2T and drop the last argument.
I've added this patch to nvme-6.16. I'm waiting for the discussion
to conclude or a resend on the others.
next prev parent reply other threads:[~2025-04-22 9:52 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 6:55 [PATCHv3 0/3] nvme-tcp: fixup I/O stall on congested sockets Hannes Reinecke
2025-04-03 6:55 ` [PATCH 1/3] nvme-tcp: open-code nvme_tcp_queue_request() for R2T Hannes Reinecke
2025-04-13 22:56 ` Sagi Grimberg
2025-04-22 8:09 ` Christoph Hellwig [this message]
2025-04-03 6:55 ` [PATCH 2/3] nvme-tcp: sanitize request list handling Hannes Reinecke
2025-04-13 23:00 ` Sagi Grimberg
2025-04-14 12:35 ` Hannes Reinecke
2025-04-14 20:29 ` Sagi Grimberg
2025-04-03 6:55 ` [PATCH 3/3] nvme-tcp: fix I/O stalls on congested sockets Hannes Reinecke
2025-04-13 23:09 ` Sagi Grimberg
2025-04-14 6:21 ` Hannes Reinecke
2025-04-14 20:24 ` Sagi Grimberg
2025-04-15 7:07 ` Hannes Reinecke
2025-04-15 21:35 ` Sagi Grimberg
2025-04-16 7:56 ` Hannes Reinecke
2025-04-16 22:09 ` Sagi Grimberg
2025-04-17 23:03 ` Kamaljit Singh
2025-04-17 23:06 ` Kamaljit Singh
2025-04-18 10:51 ` Sagi Grimberg
2025-04-18 18:55 ` Kamaljit Singh
2025-04-19 16:10 ` Sagi Grimberg
2025-04-21 19:11 ` Kamaljit Singh
2025-04-22 11:43 ` Sagi Grimberg
2025-04-23 17:26 ` Kamaljit Singh
2025-04-24 11:26 ` Hannes Reinecke
2025-04-25 21:55 ` Sagi Grimberg
2025-04-25 22:09 ` Sagi Grimberg
2025-04-25 23:47 ` Kamaljit Singh
2025-04-27 10:35 ` Sagi Grimberg
[not found] ` <BY5PR04MB6849D4BF87755B82A073BBDABC89A@BY5PR04MB6849.namprd04.prod.outlook.com>
2025-05-06 18:05 ` Hannes Reinecke
2025-05-07 22:26 ` Kamaljit Singh
2025-05-08 21:23 ` Kamaljit Singh
2025-05-09 6:52 ` Hannes Reinecke
2025-05-09 8:58 ` Hannes Reinecke
2025-05-11 9:12 ` Sagi Grimberg
2025-05-11 9:11 ` Sagi Grimberg
2025-05-13 19:24 ` Kamaljit Singh
2025-05-14 6:35 ` Hannes Reinecke
2025-05-17 10:01 ` Sagi Grimberg
2025-05-17 10:12 ` Sagi Grimberg
2025-05-27 21:49 ` Sagi Grimberg
2025-05-28 1:43 ` Kamaljit Singh
2025-05-28 6:33 ` Hannes Reinecke
2025-05-28 22:45 ` Kamaljit Singh
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=20250422080907.GA411@lst.de \
--to=hch@lst.de \
--cc=hare@kernel.org \
--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.