Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1258365 > unrolled thread

Re: Persistent Reservation API V4

Started byMike Snitzer <snitzer@redhat.com>
First post2015-10-28 19:50 +0100
Last post2015-10-28 19:50 +0100
Articles 2 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Persistent Reservation API V4 Mike Snitzer <snitzer@redhat.com> - 2015-10-28 19:50 +0100
    Re: Persistent Reservation API V4 Mike Snitzer <snitzer@redhat.com> - 2015-10-28 19:50 +0100

#1258365 — Re: Persistent Reservation API V4

FromMike Snitzer <snitzer@redhat.com>
Date2015-10-28 19:50 +0100
SubjectRe: Persistent Reservation API V4
Message-ID<qoDXk-6mo-13@gated-at.bofh.it>
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1258366

FromMike Snitzer <snitzer@redhat.com>
Date2015-10-28 19:50 +0100
Message-ID<qoDXk-6mo-17@gated-at.bofh.it>
In reply to#1258365
On Wed, Oct 28 2015 at  2:43pm -0400,
Mike Snitzer <snitzer@redhat.com> wrote:

> 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?

I should've looked at Jens' tree before asking.. I now see Jens has
for-4.4/reservations

I'll rebase accordingly and pick up the DM changes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web