[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1444911052-9423-1-git-send-email-hch@lst.de>
Date: Thu, 15 Oct 2015 14:10:46 +0200
From: Christoph Hellwig <hch@....de>
To: axboe@...com
Cc: keith.busch@...el.com, linux-scsi@...r.kernel.org,
linux-nvme@...ts.infradead.org, dm-devel@...hat.com,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Persistent Reservation API V4
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 also have a set of simple test tools available at
git://git.infradead.org/users/hch/pr-tests.git
Changes since V3:
- added NVMe support (from Keith Busch)
- add a CAP_SYS_ADMIN check for the ioctl
- trŅvial rebase to Jens' latests block tree
Changes since V2:
- added an ignore flag to the reserve opertion as well, and redid
the ioctl API to have general flags fields
- rebased on top of the latest block layer tree updates
Changes since V1:
- rename DM ->ioctl to ->prepare_ioctl
- rename dm_get_ioctl_table to dm_get_live_table_for_ioctl
- merge two DM patches into one
- various spelling fixes
--
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