From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 4/4] nvme-core: support traffic based keep-alive based on controller support
Date: Wed, 17 Oct 2018 09:05:45 +0200 [thread overview]
Message-ID: <20181017070545.GA23049@lst.de> (raw)
In-Reply-To: <20180928011537.30069-5-sagi@grimberg.me>
> + nvme_req(req)->ctrl->comp_seen = true;
shouldn't we only do this for controllers with keep a live support?
next prev parent reply other threads:[~2018-10-17 7:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 1:15 [PATCH 0/4] traffic based keep alive support (TP 4024) Sagi Grimberg
2018-09-28 1:15 ` [PATCH 1/4] nvme: introduce ctrl attributes enumeration Sagi Grimberg
2018-09-28 1:15 ` [PATCH 2/4] nvmet: support for traffic based keep-alive Sagi Grimberg
2018-09-28 1:15 ` [PATCH 3/4] nvme-core: cache controller attributes Sagi Grimberg
2018-09-28 1:15 ` [PATCH 4/4] nvme-core: support traffic based keep-alive based on controller support Sagi Grimberg
2018-10-17 7:05 ` Christoph Hellwig [this message]
2018-10-19 0:38 ` Sagi Grimberg
2018-10-19 6:00 ` Christoph Hellwig
2018-10-19 6:30 ` Sagi Grimberg
2018-10-16 1:07 ` [PATCH 0/4] traffic based keep alive support (TP 4024) Sagi Grimberg
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=20181017070545.GA23049@lst.de \
--to=hch@lst.de \
/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;
as well as URLs for NNTP newsgroup(s).