-----Original Message-----
From: Rao, Vinay 
Sent: Tuesday, May 4, 2021 2:03 PM
To: Chaitanya Kulkarni; Christoph Hellwig; Keith Busch
Cc: Belanger, Martin; Hayes, Stuart; Tarikere, Madhu; Martin Belanger; linux-nvme@lists.infradead.org; axboe@fb.com; sagi@grimberg.me
Subject: RE: [PATCH 1/1] nvme-fabrics: Generate uevent on namespace AENs



-----Original Message-----
From: Chaitanya Kulkarni <redacted> 
Sent: Tuesday, May 4, 2021 4:52 AM
To: Rao, Vinay; Christoph Hellwig; Keith Busch
Cc: Belanger, Martin; Hayes, Stuart; Tarikere, Madhu; Martin Belanger; linux-nvme@lists.infradead.org; axboe@fb.com; sagi@grimberg.me
Subject: Re: [PATCH 1/1] nvme-fabrics: Generate uevent on namespace AENs


[EXTERNAL EMAIL] 

On 5/3/21 00:21, Rao, Vinay wrote:

Forcing RAE bit on all the log pages that kernel cares about is one of the option.

Can we also think also think about an another mechanism where the kernel would generate uevent after kernel does a get log page. This would make kernel always to get the get log data first from the controller. 

to read empty log page ?

We are interested in these two events NVME_AER_NOTICE_NS_CHANGED and NVME_AER_NOTICE_ANA. 
-- NVME_AER_NOTICE_NS_CHANGED event would require the host software to do an nvme identify namespace to see the change in the namespace. 
-- NVME_AER_NOTICE_ANA event would require the host software to do a ANA LOG page command to get the ANA log page from the controller. Even if the ANA log page is sent from userland after the kernel sends it first the controller would still return the ANA log page. It will not return an empty log page. 

Any comments on my last email? 


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme