public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "amit.engel@dell.com" <amit.engel@dell.com>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] tcp: add additional info for nvme_tcp_timeout log
Date: Wed, 16 Nov 2022 18:37:22 +0000	[thread overview]
Message-ID: <048950d7-2824-28dd-cf8e-32ee16bd124e@nvidia.com> (raw)
In-Reply-To: <1668607073-1814545-1-git-send-email-amit.engel@dell.com>

On 11/16/22 05:57, amit.engel@dell.com wrote:
> From: Amit Engel <Amit.Engel@dell.com>
> 

without the commit log it is hard to understand whay additional
information is needed also you need to fix the subject line..

> Signed-off-by: Amit Engel <Amit.Engel@dell.com>
> ---
>   drivers/nvme/host/tcp.c | 7 +++++--
>   1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
> index 1eed0fc26b3a..5abaff5d6f6e 100644
> --- a/drivers/nvme/host/tcp.c
> +++ b/drivers/nvme/host/tcp.c
> @@ -2277,8 +2277,11 @@ static enum blk_eh_timer_return nvme_tcp_timeout(struct request *rq)
>   	struct nvme_tcp_cmd_pdu *pdu = req->pdu;
>   
>   	dev_warn(ctrl->device,
> -		"queue %d: timeout request %#x type %d\n",
> -		nvme_tcp_queue_id(req->queue), rq->tag, pdu->hdr.type);
> +		"queue %d: cntlid %u timeout request %#x type %d cid %u opcode %#x "
> +		"start time %lluns io start time %lluns request timeout %ums\n",
> +		nvme_tcp_queue_id(req->queue), ctrl->cntlid, rq->tag, pdu->hdr.type,
> +		pdu->cmd.common.command_id, pdu->cmd.common.opcode,
> +		ktime_sub_ns(ktime_get(), rq->start_time_ns), ktime_sub_ns(ktime_get(), rq->io_start_time_ns), jiffies_to_msecs(rq->timeout));
>   
>   	if (ctrl->state != NVME_CTRL_LIVE) {
>   		/*


  reply	other threads:[~2022-11-16 18:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 13:57 [PATCH] tcp: add additional info for nvme_tcp_timeout log amit.engel
2022-11-16 18:37 ` Chaitanya Kulkarni [this message]
2022-11-17 13:14   ` Engel, Amit
2022-11-17 13:13 ` [PATCH] nvme-tcp: " amit.engel
2022-11-20 11:59   ` Sagi Grimberg
2022-11-21 11:32     ` Engel, Amit
2022-11-21 11:36       ` Sagi Grimberg
2022-11-21 12:11         ` Engel, Amit
2022-11-21 14:34           ` Sagi Grimberg
2022-12-04 17:28             ` Engel, Amit
2022-12-05  5:38               ` Chaitanya Kulkarni
2022-12-05  9:59               ` Sagi Grimberg
2022-12-05 18:00                 ` Engel, Amit
2022-12-05 20:11                   ` Sagi Grimberg
2022-12-06 12:57                     ` Engel, Amit

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=048950d7-2824-28dd-cf8e-32ee16bd124e@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=amit.engel@dell.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox