From: Sagi Grimberg <sagi@grimberg.me>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>, "hch@lst.de" <hch@lst.de>
Cc: Guixin Liu <kanie@linux.alibaba.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH v7 1/1] nvmet: support reservation feature
Date: Sat, 23 Mar 2024 22:41:34 +0200 [thread overview]
Message-ID: <7b7fa5ab-389c-4ad7-b8cf-9b3375f7f817@grimberg.me> (raw)
In-Reply-To: <b3b90aa1-7026-4d58-9a3e-5c1ede800d94@nvidia.com>
On 22/03/2024 11:34, Chaitanya Kulkarni wrote:
> Christoph,
>
> On 3/21/2024 2:02 PM, hch@lst.de wrote:
>> On Wed, Mar 20, 2024 at 11:16:29AM +0200, Sagi Grimberg wrote:
>>> That's a neat idea, we also have file to think about though.
>> Indeed. It still would be good to avoid the extra overhead when not
>> needed, though.
> I still don't understand how this solves the case for file back-end ?
> can you please explain in detail ?
>
> as far as I can there is no equivalent provision that we can use for
> file back-end as you have suggested for block (bio/blk-mq)back-end,
> if there is can you please provide some details ?
>
> In case there is no such provision, how do you see file backends to
> handle this case ? perhaps you are referring to use above suggested
> mechanism for block backend and implement percpu-ref to for file only
> backend so we can keep the code clean for bio and passthru back-end vs
> file back-end ?
Yes, the latter.
next prev parent reply other threads:[~2024-03-23 20:41 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
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 [this message]
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=7b7fa5ab-389c-4ad7-b8cf-9b3375f7f817@grimberg.me \
--to=sagi@grimberg.me \
--cc=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).