From: Guixin Liu <kanie@linux.alibaba.com>
To: Sagi Grimberg <sagi@grimberg.me>,
hch@lst.de, kch@nvidia.com, chaitanyak@nvidia.com
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH V2 3/3] nvme: introduce pr_work to handle resv event
Date: Tue, 16 Jan 2024 17:57:30 +0800 [thread overview]
Message-ID: <2a71b2aa-7ce3-458d-a065-da38e254bbbb@linux.alibaba.com> (raw)
In-Reply-To: <0351e7e8-2bfd-4161-a4a4-1a0c521bd337@grimberg.me>
在 2024/1/16 15:59, Sagi Grimberg 写道:
>
>
> On 1/16/24 04:02, Guixin Liu wrote:
>>
>> 在 2024/1/15 16:59, Sagi Grimberg 写道:
>>>
>>>> When a reservation event is reported, the corresponding log page is
>>>> already on the target side, and the host side needs to send a get
>>>> log command to clear these log pages.
>>>
>>> AENs are already sent to userspace, I don't see why the kernel
>>> should read the log page unless it has something meaningful to
>>> do with it.
>>>
>> Is it tolerable if we dont clear the log page?
>
> Its up to the host. If the host has nothing to do with it
> then it doesn't have to do anything with it. I'm assuming
> that the user exercising reservations would listen to udev.
>
> Perhaps libnvme would be the place we want to allow users
> to consume an api to deal with reservation events.
Agree, the userspace may use the reservation log page's information,
I will do a research on libnvme to see if we can add a consuming api after
this is done.
next prev parent reply other threads:[~2024-01-16 9:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 9:23 [PATCH V2 0/3] *** Implement the NVMe reservation feature *** Guixin Liu
2024-01-14 9:23 ` [PATCH V2 1/3] nvmet: support reservation feature Guixin Liu
2024-01-15 9:26 ` Sagi Grimberg
2024-01-16 2:16 ` Guixin Liu
2024-01-14 9:23 ` [PATCH V2 2/3] nvmet: unify aer type enum Guixin Liu
2024-01-15 9:03 ` Sagi Grimberg
2024-01-14 9:23 ` [PATCH V2 3/3] nvme: introduce pr_work to handle resv event Guixin Liu
2024-01-15 8:59 ` Sagi Grimberg
2024-01-16 2:02 ` Guixin Liu
2024-01-16 7:59 ` Sagi Grimberg
2024-01-16 9:57 ` Guixin Liu [this message]
2024-01-15 9:51 ` [PATCH V2 0/3] *** Implement the NVMe reservation feature *** Sagi Grimberg
2024-01-16 2:29 ` Guixin Liu
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=2a71b2aa-7ce3-458d-a065-da38e254bbbb@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox