All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Bart Van Assche <bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>
Cc: device-mapper development
	<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	axboe-b10kYP2dOMg@public.gmane.org,
	linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	keith.busch-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: [dm-devel] [PATCH 3/6] sd: implement the Persistent Reservation API
Date: Thu, 15 Oct 2015 17:32:27 +0200	[thread overview]
Message-ID: <20151015153227.GA3536@lst.de> (raw)
In-Reply-To: <561FC6AA.3080508-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org>

On Thu, Oct 15, 2015 at 08:30:50AM -0700, Bart Van Assche wrote:
> 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 ?

In theory it does.  In practice it's only used by disks/arrays and tapes,
and as tapes don't have a struct block_device this isn't going to be useful
for them.

WARNING: multiple messages have this Message-ID (diff)
From: hch@lst.de (Christoph Hellwig)
Subject: [dm-devel] [PATCH 3/6] sd: implement the Persistent Reservation API
Date: Thu, 15 Oct 2015 17:32:27 +0200	[thread overview]
Message-ID: <20151015153227.GA3536@lst.de> (raw)
In-Reply-To: <561FC6AA.3080508@sandisk.com>

On Thu, Oct 15, 2015@08:30:50AM -0700, Bart Van Assche wrote:
> 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 ?

In theory it does.  In practice it's only used by disks/arrays and tapes,
and as tapes don't have a struct block_device this isn't going to be useful
for them.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Bart Van Assche <bart.vanassche@sandisk.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	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
Subject: Re: [dm-devel] [PATCH 3/6] sd: implement the Persistent Reservation API
Date: Thu, 15 Oct 2015 17:32:27 +0200	[thread overview]
Message-ID: <20151015153227.GA3536@lst.de> (raw)
In-Reply-To: <561FC6AA.3080508@sandisk.com>

On Thu, Oct 15, 2015 at 08:30:50AM -0700, Bart Van Assche wrote:
> 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 ?

In theory it does.  In practice it's only used by disks/arrays and tapes,
and as tapes don't have a struct block_device this isn't going to be useful
for them.

  parent reply	other threads:[~2015-10-15 15:32 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   ` [dm-devel] " Bart Van Assche
2015-10-15 15:30     ` 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 [this message]
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=20151015153227.GA3536@lst.de \
    --to=hch-jcswghmuv9g@public.gmane.org \
    --cc=axboe-b10kYP2dOMg@public.gmane.org \
    --cc=bart.vanassche-XdAiOPVOjttBDgjK7y7TUQ@public.gmane.org \
    --cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=keith.busch-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nvme-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.