From: Mike Snitzer <snitzer-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Cc: axboe-b10kYP2dOMg@public.gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
keith.busch-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: Persistent Reservation API V4
Date: Wed, 28 Oct 2015 14:43:56 -0400 [thread overview]
Message-ID: <20151028184356.GA21933@redhat.com> (raw)
In-Reply-To: <1444911052-9423-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
On Thu, Oct 15 2015 at 8:10am -0400,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org> wrote:
> This series adds support for a simplified Persistent Reservation API
> to the block layer. The intent is that both in-kernel and userspace
> consumers can use the API instead of having to hand craft SCSI or NVMe
> command through the various pass through interfaces. It also adds
> DM support as getting reservations through dm-multipath is a major
> pain with the current scheme.
>
> The ioctl API is documented in Documentation/block/pr.txt, but to
> fully understand the concept you'll have to read up the SPC spec,
> PRs are too complicated that trying to rephrase them into different
> terminology is just going to create confusion.
>
> Note that Mike wants to include the DM patches so through the DM
> tree, so they are only included for reference.
I looked at these again and the DM changes look good. Any update on
if/when the block changes will land?
WARNING: multiple messages have this Message-ID (diff)
From: snitzer@redhat.com (Mike Snitzer)
Subject: Persistent Reservation API V4
Date: Wed, 28 Oct 2015 14:43:56 -0400 [thread overview]
Message-ID: <20151028184356.GA21933@redhat.com> (raw)
In-Reply-To: <1444911052-9423-1-git-send-email-hch@lst.de>
On Thu, Oct 15 2015 at 8:10am -0400,
Christoph Hellwig <hch@lst.de> wrote:
> This series adds support for a simplified Persistent Reservation API
> to the block layer. The intent is that both in-kernel and userspace
> consumers can use the API instead of having to hand craft SCSI or NVMe
> command through the various pass through interfaces. It also adds
> DM support as getting reservations through dm-multipath is a major
> pain with the current scheme.
>
> The ioctl API is documented in Documentation/block/pr.txt, but to
> fully understand the concept you'll have to read up the SPC spec,
> PRs are too complicated that trying to rephrase them into different
> terminology is just going to create confusion.
>
> Note that Mike wants to include the DM patches so through the DM
> tree, so they are only included for reference.
I looked at these again and the DM changes look good. Any update on
if/when the block changes will land?
WARNING: multiple messages have this Message-ID (diff)
From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: axboe@fb.com, linux-scsi@vger.kernel.org,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-nvme@lists.infradead.org, keith.busch@intel.com,
dm-devel@redhat.com
Subject: Re: Persistent Reservation API V4
Date: Wed, 28 Oct 2015 14:43:56 -0400 [thread overview]
Message-ID: <20151028184356.GA21933@redhat.com> (raw)
In-Reply-To: <1444911052-9423-1-git-send-email-hch@lst.de>
On Thu, Oct 15 2015 at 8:10am -0400,
Christoph Hellwig <hch@lst.de> wrote:
> This series adds support for a simplified Persistent Reservation API
> to the block layer. The intent is that both in-kernel and userspace
> consumers can use the API instead of having to hand craft SCSI or NVMe
> command through the various pass through interfaces. It also adds
> DM support as getting reservations through dm-multipath is a major
> pain with the current scheme.
>
> The ioctl API is documented in Documentation/block/pr.txt, but to
> fully understand the concept you'll have to read up the SPC spec,
> PRs are too complicated that trying to rephrase them into different
> terminology is just going to create confusion.
>
> Note that Mike wants to include the DM patches so through the DM
> tree, so they are only included for reference.
I looked at these again and the DM changes look good. Any update on
if/when the block changes will land?
next prev parent reply other threads:[~2015-10-28 18:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 12:10 Persistent Reservation API V4 Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 1/6] block: cleanup blkdev_ioctl Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 2/6] block: add an API for Persistent Reservations Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 3/6] sd: implement the Persistent Reservation API Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 15:30 ` [dm-devel] " Bart Van Assche
2015-10-15 15:30 ` Bart Van Assche
2015-10-15 15:30 ` Bart Van Assche
[not found] ` <561FC6AA.3080508-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-10-15 15:32 ` Christoph Hellwig
2015-10-15 15:32 ` Christoph Hellwig
2015-10-15 15:32 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 4/6] dm: refactor ioctl handling Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 5/6] dm: add support for passing through persistent reservations Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 6/6] NVMe: Add persistent reservation ops Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
[not found] ` <1444911052-9423-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-10-28 18:43 ` Mike Snitzer [this message]
2015-10-28 18:43 ` Persistent Reservation API V4 Mike Snitzer
2015-10-28 18:43 ` Mike Snitzer
2015-10-28 18:48 ` Mike Snitzer
2015-10-28 18:48 ` Mike Snitzer
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=20151028184356.GA21933@redhat.com \
--to=snitzer-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=axboe-b10kYP2dOMg@public.gmane.org \
--cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=hch-jcswGhMUV9g@public.gmane.org \
--cc=keith.busch-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.