From: Bart Van Assche <bart.vanassche@sandisk.com>
To: device-mapper development <dm-devel@redhat.com>, axboe@fb.com
Cc: linux-scsi@vger.kernel.org, linux-api@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org,
keith.busch@intel.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [dm-devel] [PATCH 3/6] sd: implement the Persistent Reservation API
Date: Thu, 15 Oct 2015 08:30:50 -0700 [thread overview]
Message-ID: <561FC6AA.3080508@sandisk.com> (raw)
In-Reply-To: <1444911052-9423-4-git-send-email-hch@lst.de>
On 10/15/2015 05:10 AM, Christoph Hellwig wrote:
> This is a mostly trivial mapping to the PERSISTENT RESERVE IN/OUT
> commands.
Hello Christoph,
Can you explain why this functionality has been added to the sd driver
instead of the SCSI core ? Aren't persistent reservations a concept that
applies to all SCSI device types ?
Thanks,
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: bart.vanassche@sandisk.com (Bart Van Assche)
Subject: [dm-devel] [PATCH 3/6] sd: implement the Persistent Reservation API
Date: Thu, 15 Oct 2015 08:30:50 -0700 [thread overview]
Message-ID: <561FC6AA.3080508@sandisk.com> (raw)
In-Reply-To: <1444911052-9423-4-git-send-email-hch@lst.de>
On 10/15/2015 05:10 AM, Christoph Hellwig wrote:
> This is a mostly trivial mapping to the PERSISTENT RESERVE IN/OUT
> commands.
Hello Christoph,
Can you explain why this functionality has been added to the sd driver
instead of the SCSI core ? Aren't persistent reservations a concept that
applies to all SCSI device types ?
Thanks,
Bart.
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <bart.vanassche@sandisk.com>
To: device-mapper development <dm-devel@redhat.com>, <axboe@fb.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-api@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-nvme@lists.infradead.org>,
<keith.busch@intel.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [dm-devel] [PATCH 3/6] sd: implement the Persistent Reservation API
Date: Thu, 15 Oct 2015 08:30:50 -0700 [thread overview]
Message-ID: <561FC6AA.3080508@sandisk.com> (raw)
In-Reply-To: <1444911052-9423-4-git-send-email-hch@lst.de>
On 10/15/2015 05:10 AM, Christoph Hellwig wrote:
> This is a mostly trivial mapping to the PERSISTENT RESERVE IN/OUT
> commands.
Hello Christoph,
Can you explain why this functionality has been added to the sd driver
instead of the SCSI core ? Aren't persistent reservations a concept that
applies to all SCSI device types ?
Thanks,
Bart.
next prev parent reply other threads:[~2015-10-15 15:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 12:10 Persistent Reservation API V4 Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 1/6] block: cleanup blkdev_ioctl Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 2/6] block: add an API for Persistent Reservations Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 3/6] sd: implement the Persistent Reservation API Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 15:30 ` Bart Van Assche [this message]
2015-10-15 15:30 ` [dm-devel] " Bart Van Assche
2015-10-15 15:30 ` Bart Van Assche
[not found] ` <561FC6AA.3080508-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
2015-10-15 15:32 ` Christoph Hellwig
2015-10-15 15:32 ` Christoph Hellwig
2015-10-15 15:32 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 4/6] dm: refactor ioctl handling Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 5/6] dm: add support for passing through persistent reservations Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
2015-10-15 12:10 ` [PATCH 6/6] NVMe: Add persistent reservation ops Christoph Hellwig
2015-10-15 12:10 ` Christoph Hellwig
[not found] ` <1444911052-9423-1-git-send-email-hch-jcswGhMUV9g@public.gmane.org>
2015-10-28 18:43 ` Persistent Reservation API V4 Mike Snitzer
2015-10-28 18:43 ` Mike Snitzer
2015-10-28 18:43 ` Mike Snitzer
2015-10-28 18:48 ` Mike Snitzer
2015-10-28 18:48 ` Mike Snitzer
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=561FC6AA.3080508@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@fb.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=keith.busch@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.