From mboxrd@z Thu Jan 1 00:00:00 1970 From: keith.busch@intel.com (Keith Busch) Date: Wed, 5 Dec 2018 13:41:14 -0700 Subject: Whenever running nvme discover command, syslog shows warning messages In-Reply-To: <6706f7c0-ff70-0ebb-77a9-a2e24d01c901@grimberg.me> References: <7a1a884d-5be0-064a-0865-51bca20ba919@grimberg.me> <4fb9c4fc-e5ce-2238-fbcf-1fdd6da10e23@broadcom.com> <20181205154359.GA18064@localhost.localdomain> <6706f7c0-ff70-0ebb-77a9-a2e24d01c901@grimberg.me> Message-ID: <20181205204114.GA18383@localhost.localdomain> 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.