From: Guixin Liu <kanie@linux.alibaba.com>
To: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>
Cc: hch@lst.de, kch@nvidia.com, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v7 1/1] nvmet: support reservation feature
Date: Wed, 13 Mar 2024 11:42:12 +0800 [thread overview]
Message-ID: <2eb0672e-1073-497b-94ce-f3c356b7580e@linux.alibaba.com> (raw)
In-Reply-To: <47f18beb-3647-4464-9f2c-b75e10ec346b@grimberg.me>
在 2024/3/13 05:31, Sagi Grimberg 写道:
> So I understand from you that there is out-of-band mechanism for fence
> guarantee?
>
> In any event, Christoph reminded me that preempt and abort is
> mandatory, so we cannot
> get away without doing it.
>
Agree.
> I suggest to introduce a per-ns-per-controller percpuref, with an
> xarray that is rcu protected.
I will implement it in v9, and I also think that we should a
time-limited wait.
>
> btw, I also think that reservations on nsid=0xffffffff should also
> work. IIRC there were at least
> two use-cases that would have benefited from reservations on all
> subsystem namespaces.
> It can also be a lot more lightweight to implement that (outside of
> conflicting reservations checks).
You mean one host can reserve all of namespaces by sending one
reservation command?
Well, Could you please tell me which two use-cases?
I think this will make the target code too complicated, because the
reservation situation on each
namespace may different, we should handle it one-by-one, and if failed
in middle, we should revert
the handled namespaces.
Best regards,
Guixin Liu
next prev parent reply other threads:[~2024-03-13 3:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 2:32 [PATCH v7 0/1] Implement the NVMe reservation feature Guixin Liu
2024-02-01 2:32 ` [PATCH v7 1/1] nvmet: support " Guixin Liu
2024-02-28 0:40 ` Sagi Grimberg
2024-02-28 2:21 ` Guixin Liu
2024-02-28 3:21 ` Keith Busch
2024-02-28 3:40 ` Guixin Liu
2024-03-07 9:27 ` Sagi Grimberg
2024-03-07 9:42 ` Guixin Liu
2024-03-08 9:15 ` Guixin Liu
2024-03-08 10:07 ` Sagi Grimberg
2024-03-11 11:19 ` Guixin Liu
2024-03-12 21:31 ` Sagi Grimberg
2024-03-13 3:42 ` Guixin Liu [this message]
2024-03-13 9:54 ` Sagi Grimberg
2024-03-13 11:56 ` Guixin Liu
2024-03-13 12:36 ` Sagi Grimberg
2024-03-14 2:03 ` Guixin Liu
2024-03-19 2:59 ` Chaitanya Kulkarni
2024-03-19 3:19 ` Guixin Liu
2024-03-20 1:59 ` hch
2024-03-20 9:16 ` Sagi Grimberg
2024-03-21 8:06 ` Chaitanya Kulkarni
2024-03-21 21:02 ` hch
2024-03-22 9:34 ` Chaitanya Kulkarni
2024-03-23 20:41 ` Sagi Grimberg
2024-02-18 2:12 ` [PATCH v7 0/1] Implement the NVMe " Guixin Liu
2024-02-26 6:33 ` Guixin Liu
2024-02-26 6:43 ` Chaitanya Kulkarni
2024-02-29 2:57 ` 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=2eb0672e-1073-497b-94ce-f3c356b7580e@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--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