From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756159AbbJ1SoA (ORCPT ); Wed, 28 Oct 2015 14:44:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57807 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752821AbbJ1Sn6 (ORCPT ); Wed, 28 Oct 2015 14:43:58 -0400 Date: Wed, 28 Oct 2015 14:43:56 -0400 From: Mike Snitzer To: Christoph Hellwig 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 Message-ID: <20151028184356.GA21933@redhat.com> References: <1444911052-9423-1-git-send-email-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1444911052-9423-1-git-send-email-hch@lst.de> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 15 2015 at 8:10am -0400, Christoph Hellwig 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?