From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@intel.com>,
Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Hannes Reinecke <hare@suse.de>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v4 2/2] nvme: add tracepoint for nvme_complete_rq
Date: Mon, 22 Jan 2018 14:35:23 -0500 [thread overview]
Message-ID: <yq18tcplm9w.fsf@oracle.com> (raw)
In-Reply-To: <20180122153040.2myfgm7hvjtd5n3d@linux-x5ow.site> (Johannes Thumshirn's message of "Mon, 22 Jan 2018 16:30:41 +0100")
Johannes,
> On Mon, Jan 22, 2018 at 04:23:40PM +0100, Christoph Hellwig wrote:
>> Wouldn't some indication on which queue this completion happens
>> be useful?
>
> Probably yes. I'll add it in v5.
Yes, that would be great. I always end up having to use custom printks
for this.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-01-22 20:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 14:18 [PATCH v4 0/2] add tracepoints for nvme command submission and completion Johannes Thumshirn
2018-01-19 14:18 ` [PATCH v4 1/2] nvme: add tracepoint for nvme_setup_cmd Johannes Thumshirn
2018-01-22 15:23 ` Christoph Hellwig
2018-01-22 15:53 ` Johannes Thumshirn
2018-01-22 15:59 ` Christoph Hellwig
2018-01-22 16:04 ` Johannes Thumshirn
2018-01-22 16:10 ` Christoph Hellwig
2018-01-22 16:15 ` Johannes Thumshirn
2018-01-19 14:18 ` [PATCH v4 2/2] nvme: add tracepoint for nvme_complete_rq Johannes Thumshirn
2018-01-22 15:23 ` Christoph Hellwig
2018-01-22 15:30 ` Johannes Thumshirn
2018-01-22 19:35 ` Martin K. Petersen [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=yq18tcplm9w.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox