linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Jens Axboe <axboe@fb.com>
Cc: linux-scsi@vger.kernel.org, linux-nvme@lists.infradead.org,
	dm-devel@redhat.com, linux-api@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Persistent Reservation API
Date: Tue,  4 Aug 2015 09:11:05 +0200	[thread overview]
Message-ID: <1438672271-11309-1-git-send-email-hch@lst.de> (raw)

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.

NVMe support currently isn't included as I don't have a multihost
NVMe setup to test on, but if I can find a volunteer to test it I'm
happy to write the code for it.

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.

I also have a set of simple test tools available at:

	git://git.infradead.org/users/hch/pr-tests.git


             reply	other threads:[~2015-08-04  7:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  7:11 Christoph Hellwig [this message]
2015-08-04  7:11 ` [PATCH 1/6] block: cleanup blkdev_ioctl Christoph Hellwig
     [not found]   ` <1438672271-11309-2-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-08-12  0:29     ` Martin K. Petersen
2015-08-04  7:11 ` [PATCH 2/6] block: add a API for persistent reservations Christoph Hellwig
     [not found]   ` <1438672271-11309-3-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-08-12  0:45     ` Martin K. Petersen
2015-08-04  7:11 ` [PATCH 3/6] sd: implement the persisten reservation API Christoph Hellwig
     [not found]   ` <1438672271-11309-4-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-08-12  0:57     ` Martin K. Petersen
2015-08-04  7:11 ` [PATCH 4/6] dm: refactor ioctl handling Christoph Hellwig
     [not found]   ` <1438672271-11309-5-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-08-04 17:56     ` Mike Snitzer
2015-08-06 13:45       ` Christoph Hellwig
2015-08-04  7:11 ` [PATCH 5/6] dm: split out a helper to find the ioctl target Christoph Hellwig
     [not found]   ` <1438672271-11309-6-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-08-04 18:05     ` Mike Snitzer
     [not found]       ` <20150804180558.GB28971-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-08-06 13:45         ` Christoph Hellwig
2015-08-04  7:11 ` [PATCH 6/6] dm: add support for passing through persistent reservations Christoph Hellwig
2015-08-04 17:53 ` Persistent Reservation API Mike Snitzer
2015-08-06 13:44   ` Christoph Hellwig
2015-08-04 18:04 ` Keith Busch
2015-08-06 13:45   ` Christoph Hellwig

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=1438672271-11309-1-git-send-email-hch@lst.de \
    --to=hch@lst.de \
    --cc=axboe@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@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).