linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@fb.com>,
	linux-api@vger.kernel.org, dm-devel@redhat.com,
	linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Persistent Reservation API
Date: Tue, 4 Aug 2015 13:53:49 -0400	[thread overview]
Message-ID: <20150804175349.GA29013@redhat.com> (raw)
In-Reply-To: <1438672271-11309-1-git-send-email-hch@lst.de>

On Tue, Aug 04 2015 at  3:11am -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 DM changes need to go through linux-dm.git.  Once the block and SCSI
bits land I'll rebase accordingly.  That cross-maintainer logisitics
aside, I'll reply with feedback on the DM patches.

  parent reply	other threads:[~2015-08-04 17:53 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  7:11 Persistent Reservation API Christoph Hellwig
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 ` Mike Snitzer [this message]
2015-08-06 13:44   ` Persistent Reservation API Christoph Hellwig
2015-08-04 18:04 ` Keith Busch
2015-08-06 13:45   ` Christoph Hellwig
2015-08-11  9:30 ` David Disseldorp
2015-08-11 12:26   ` Christoph Hellwig
2015-08-11 12:52     ` David Disseldorp
2015-08-26 12:45   ` Hannes Reinecke

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=20150804175349.GA29013@redhat.com \
    --to=snitzer@redhat.com \
    --cc=axboe@fb.com \
    --cc=dm-devel@redhat.com \
    --cc=hch@lst.de \
    --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).