From: keith.busch@intel.com (Keith Busch)
Subject: Whenever running nvme discover command, syslog shows warning messages
Date: Wed, 5 Dec 2018 08:43:59 -0700 [thread overview]
Message-ID: <20181205154359.GA18064@localhost.localdomain> (raw)
In-Reply-To: <BN6PR1301MB2001C46B2AA0738A52AEDD6885AF0@BN6PR1301MB2001.namprd13.prod.outlook.com>
On Tue, Dec 04, 2018@10:27:26PM +0000, Ching-Chiao Chang wrote:
> It is not test case, we would like to run nvme discover in loop in an
> initiator, and whenever there is an NVMe volume can be attached, the
> the initiator can discover it and connect it automatically.
Polling for infrequent events is silly. Can we get an asynchronous event
notification for this? I don't see any exiting events pointing back to
the discovery log page, so maybe there's a TP opprotunity here.
next prev parent reply other threads:[~2018-12-05 15:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 0:50 Whenever running nvme discover command, syslog shows warning messages Ching-Chiao Chang
2018-11-29 17:01 ` James Smart
2018-11-30 1:34 ` Sagi Grimberg
2018-11-30 2:40 ` Ching-Chiao Chang
2018-11-30 18:48 ` James Smart
2018-12-04 22:27 ` Ching-Chiao Chang
2018-12-05 1:25 ` James Smart
2018-12-11 17:30 ` Ching-Chiao Chang
2018-12-05 15:43 ` Keith Busch [this message]
2018-12-05 20:25 ` Sagi Grimberg
2018-12-05 20:41 ` 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=20181205154359.GA18064@localhost.localdomain \
--to=keith.busch@intel.com \
/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