public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Guixin Liu <kanie@linux.alibaba.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	Sagi Grimberg <sagi@grimberg.me>
Cc: "hch@lst.de" <hch@lst.de>,
	"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: Tue, 19 Mar 2024 11:19:50 +0800	[thread overview]
Message-ID: <b691ccf2-3627-402c-bb68-eb3fc8845e41@linux.alibaba.com> (raw)
In-Reply-To: <cea98ed9-6b65-4475-8497-62f1ca9f81a3@nvidia.com>


在 2024/3/19 10:59, Chaitanya Kulkarni 写道:
> On 3/13/24 19:03, Guixin Liu wrote:
>>
>>> Didn't say this is actually in use, but a use-case that would benefit.
>> I will add a TODO-list to research main cluster softwares
>>
>> to see if this is actually a significant use-case, after my patch merged.
>>
>> I'll change my code then.
>>
>> Best regards,
>>
>> Guixin Liu
>>
> so which one is the latest version I use for testing ? I want to run some
> tests so I can provide reviewed-by tag ...
>
> -ck

I am adding a per-controller percpu-ref to ns to implement 
preempt_and_abort, the v9 will be soon.

Thanks,

Guixin Liu

>


  reply	other threads:[~2024-03-19  3:20 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 [this message]
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=b691ccf2-3627-402c-bb68-eb3fc8845e41@linux.alibaba.com \
    --to=kanie@linux.alibaba.com \
    --cc=chaitanyak@nvidia.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --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