[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20151028184833.GA21955@redhat.com>
Date: Wed, 28 Oct 2015 14:48:33 -0400
From: Mike Snitzer <snitzer@...hat.com>
To: Christoph Hellwig <hch@....de>
Cc: axboe@...com, linux-scsi@...r.kernel.org,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, keith.busch@...el.com,
dm-devel@...hat.com
Subject: Re: Persistent Reservation API V4
On Wed, Oct 28 2015 at 2:43pm -0400,
Mike Snitzer <snitzer@...hat.com> wrote:
> On Thu, Oct 15 2015 at 8:10am -0400,
> Christoph Hellwig <hch@....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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists