All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: Whenever running nvme discover command, syslog shows warning messages
Date: Wed, 5 Dec 2018 13:41:14 -0700	[thread overview]
Message-ID: <20181205204114.GA18383@localhost.localdomain> (raw)
In-Reply-To: <6706f7c0-ff70-0ebb-77a9-a2e24d01c901@grimberg.me>

On Wed, Dec 05, 2018@12:25:16PM -0800, Sagi Grimberg 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.
> 
> There is already an existing ratified TP, and patches for both the
> host and the target were submitted [1,2] (target got accepted), the host
> part just needs some unification for FC and the rest of the transports.
> 
> [1]:
> http://lists.infradead.org/pipermail/linux-nvme/2018-October/020232.html
> 
> [2]:
> http://lists.infradead.org/pipermail/linux-nvme/2018-October/020246.html

Cool, that's a better solution than culling the logs.

      reply	other threads:[~2018-12-05 20:41 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
2018-12-05 20:25             ` Sagi Grimberg
2018-12-05 20:41               ` Keith Busch [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=20181205204114.GA18383@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.