From: Karel Zak <kzak@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>
Cc: Christoph Hellwig <hch@infradead.org>, util-linux@vger.kernel.org
Subject: Re: [PATCH] blkpr: add block persistent reservations command
Date: Wed, 6 Apr 2022 10:55:21 +0200 [thread overview]
Message-ID: <20220406085521.nbytfauspc6kgofd@ws.net.home> (raw)
In-Reply-To: <f9e3fb29-a4ee-06a8-238f-ef1caade0234@bytedance.com>
On Wed, Apr 06, 2022 at 10:13:00AM +0800, zhenwei pi wrote:
> On 4/5/22 15:14, Christoph Hellwig wrote:
> > Any reason this never got picked up or commented on?
> > This seems to have been ignored.
>
> Hi Karel,
> Could you please give me any hint?
Frankly, I see this first time and I cannot found 'blkpr' in my
emails ... but I see it in mailing list archive(s) now, for example
https://lore.kernel.org/all/20210916032901.2189336-1-pizhenwei@bytedance.com/,
so it's probably my mistake. Sorry for this ;-(
At first glance it seems like something I can merge.
Karel
> > On Thu, Sep 16, 2021 at 11:29:01AM +0800, zhenwei pi wrote:
> > > Linux kernel block layer supports PR (persistent reservations) ioctl
> > > on a block device. Typically SCSI and NVMe disk support PR feature,
> > > and blkpr could operation on them.
> > >
> > > Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> > > ---
> > > configure.ac | 11 ++
> > > sys-utils/Makemodule.am | 8 ++
> > > sys-utils/blkpr.8.adoc | 64 ++++++++++
> > > sys-utils/blkpr.c | 277 ++++++++++++++++++++++++++++++++++++++++
> > > 4 files changed, 360 insertions(+)
> > > create mode 100644 sys-utils/blkpr.8.adoc
> > > create mode 100644 sys-utils/blkpr.c
> --
> zhenwei pi
>
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2022-04-06 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 3:29 [PATCH] blkpr: add block persistent reservations command zhenwei pi
2021-09-23 2:18 ` PING: " zhenwei pi
2022-04-05 7:14 ` Christoph Hellwig
2022-04-06 2:13 ` zhenwei pi
2022-04-06 8:55 ` Karel Zak [this message]
2022-04-06 10:27 ` Karel Zak
2022-04-07 3:51 ` zhenwei pi
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=20220406085521.nbytfauspc6kgofd@ws.net.home \
--to=kzak@redhat.com \
--cc=hch@infradead.org \
--cc=pizhenwei@bytedance.com \
--cc=util-linux@vger.kernel.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 NNTP newsgroup(s).