All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Rao, Vinay" <Vinay.Rao@dell.com>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
	Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>
Cc: "Belanger, Martin" <Martin.Belanger@dell.com>,
	"Hayes, Stuart" <Stuart.Hayes@dell.com>,
	"Tarikere, Madhu" <Madhu.Tarikere@dell.com>,
	Martin Belanger <nitram_67@hotmail.com>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	"axboe@fb.com" <axboe@fb.com>,
	"sagi@grimberg.me" <sagi@grimberg.me>
Subject: RE: [PATCH 1/1] nvme-fabrics: Generate uevent on namespace AENs
Date: Tue, 11 May 2021 08:53:00 +0000	[thread overview]
Message-ID: <BYAPR19MB293589E3A1359CD15964AACF8F539@BYAPR19MB2935.namprd19.prod.outlook.com> (raw)
In-Reply-To: <BYAPR19MB29358DD73BFD034E84C9602A8F5A9@BYAPR19MB2935.namprd19.prod.outlook.com>



-----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 <Chaitanya.Kulkarni@wdc.com> 
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

  reply	other threads:[~2021-05-11 12:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28 20:18 [PATCH 1/1] nvme-fabrics: Generate uevent on namespace AENs Martin Belanger
2021-04-29  1:18 ` Chaitanya Kulkarni
2021-04-29  1:24 ` Chaitanya Kulkarni
2021-04-29  6:30 ` Christoph Hellwig
2021-04-29 16:58   ` Belanger, Martin
2021-04-29 18:22     ` Chaitanya Kulkarni
2021-04-30  5:14       ` Rao, Vinay
2021-04-30 16:21         ` Keith Busch
2021-05-03  6:52           ` Christoph Hellwig
2021-05-03  7:20             ` Rao, Vinay
2021-05-03 23:20               ` Chaitanya Kulkarni
2021-05-03 23:21               ` Chaitanya Kulkarni
2021-05-04  8:32                 ` Rao, Vinay
2021-05-11  8:53                   ` Rao, Vinay [this message]
2021-06-16 10:38             ` Rao, Vinay
2021-06-24  9:10             ` Hannes Reinecke
2021-06-24  9:17             ` Hannes Reinecke
2021-06-24 10:49           ` Hannes Reinecke
2021-06-30 14:00             ` Rao, Vinay

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=BYAPR19MB293589E3A1359CD15964AACF8F539@BYAPR19MB2935.namprd19.prod.outlook.com \
    --to=vinay.rao@dell.com \
    --cc=Chaitanya.Kulkarni@wdc.com \
    --cc=Madhu.Tarikere@dell.com \
    --cc=Martin.Belanger@dell.com \
    --cc=Stuart.Hayes@dell.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=nitram_67@hotmail.com \
    --cc=sagi@grimberg.me \
    /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.