From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Michael Liang <mliang@purestorage.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Cc: Mohamed Khalfella <mkhalfella@purestorage.com>,
Randy Jennings <randyj@purestorage.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvme-tcp: wait socket wmem to drain in queue stop
Date: Tue, 8 Apr 2025 21:00:00 +0000 [thread overview]
Message-ID: <612d817f-33e1-4e2d-99eb-0ea87e1a958c@nvidia.com> (raw)
In-Reply-To: <20250405054848.3773471-1-mliang@purestorage.com>
On 4/4/25 22:48, Michael Liang wrote:
> +static void nvme_tcp_stop_queue_wait(struct nvme_tcp_queue *queue)
> +{
> + int timeout = 100;
> +
is there a guarantee that above will work for all the setups?
using configurable timeout values helps creating more generic
fix, do we need to consider that here ?
> + while (timeout > 0) {
> + if (!sk_wmem_alloc_get(queue->sock->sk))
> + return;
> + msleep(2);
> + timeout -= 2;
> + }
> + dev_warn(queue->ctrl->ctrl.device,
> + "qid %d: wait draining sock wmem allocation timeout\n",
> + nvme_tcp_queue_id(queue));
> +}
> +
-ck
next prev parent reply other threads:[~2025-04-08 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 5:48 [PATCH] nvme-tcp: wait socket wmem to drain in queue stop Michael Liang
2025-04-08 21:00 ` Chaitanya Kulkarni [this message]
2025-04-17 5:12 ` Michael Liang
2025-04-08 21:07 ` Randy Jennings
2025-04-17 1:46 ` Michael Liang
2025-04-13 22:25 ` Sagi Grimberg
2025-04-17 0:29 ` Michael Liang
2025-04-17 7:10 ` [PATCH v2 0/1] " Michael Liang
2025-04-17 7:13 ` [PATCH v2 1/1] " Michael Liang
2025-04-18 11:30 ` Sagi Grimberg
2025-04-18 11:49 ` Sagi Grimberg
2025-04-18 17:52 ` Michael Liang
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=612d817f-33e1-4e2d-99eb-0ea87e1a958c@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mkhalfella@purestorage.com \
--cc=mliang@purestorage.com \
--cc=randyj@purestorage.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox