From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: "Rao, Vinay" <Vinay.Rao@dell.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: Mon, 3 May 2021 23:21:47 +0000 [thread overview]
Message-ID: <BYAPR04MB4965C4F33AC9A888930DB272865B9@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: BN8PR19MB29290320440FE9740E699BAC8F5B9@BN8PR19MB2929.namprd19.prod.outlook.com
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 ?
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-05-03 23:22 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 [this message]
2021-05-04 8:32 ` Rao, Vinay
2021-05-11 8:53 ` Rao, Vinay
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=BYAPR04MB4965C4F33AC9A888930DB272865B9@BYAPR04MB4965.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=Madhu.Tarikere@dell.com \
--cc=Martin.Belanger@dell.com \
--cc=Stuart.Hayes@dell.com \
--cc=Vinay.Rao@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.