From: James Smart <james.smart@broadcom.com>
To: Johannes Thumshirn <jthumshirn@suse.de>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <keith.busch@intel.com>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
Linux NVMe Mailinglist <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH v5 1/2] nvme: cache struct nvme_ctrl reference to struct nvme_request
Date: Wed, 27 Jun 2018 09:40:29 -0700 [thread overview]
Message-ID: <7233e4f1-eee9-9849-be44-604aa11fffb3@broadcom.com> (raw)
In-Reply-To: <20180627125324.22064-2-jthumshirn@suse.de>
On 6/27/2018 5:53 AM, Johannes Thumshirn wrote:
> From: Sagi Grimberg <sagi@grimberg.me>
>
> We will need to reference the controller in the setup and completion
> time for tracing and future traffic based keep alive support.
>
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
>
> ---
> Changes to v4:
> - Move caching from nvme_setup_cmd to .init_request (Keith)
> ---
> drivers/nvme/host/core.c | 1 +
> drivers/nvme/host/fc.c | 1 +
> drivers/nvme/host/nvme.h | 1 +
> drivers/nvme/host/pci.c | 2 ++
> drivers/nvme/host/rdma.c | 1 +
> drivers/nvme/target/loop.c | 1 +
> 6 files changed, 7 insertions(+)
>
> diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c
> index e541fe268bcf..99dd62c1076c 100644
>
good for the fc side...
Reviewed-by: James Smart <james.smart@broadcom.com>
next prev parent reply other threads:[~2018-06-27 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 12:53 [PATCH v5 0/2] nvme: add controller id and disk name to tracepoints Johannes Thumshirn
2018-06-27 12:53 ` [PATCH v5 1/2] nvme: cache struct nvme_ctrl reference to struct nvme_request Johannes Thumshirn
2018-06-27 16:40 ` James Smart [this message]
2018-06-27 12:53 ` [PATCH v5 2/2] nvme: trace: add disk name to tracepoints Johannes Thumshirn
2018-06-27 16:37 ` Keith Busch
2018-06-28 7:48 ` Johannes Thumshirn
2018-06-28 20:55 ` 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=7233e4f1-eee9-9849-be44-604aa11fffb3@broadcom.com \
--to=james.smart@broadcom.com \
--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
all inboxes | Powered by JetHome®