Re: Persistent Reservation API V3

2015-08-29 Thread Christoph Hellwig
On Fri, Aug 28, 2015 at 08:33:24PM -0500, Jeremy Linton wrote: > Hello, > So, looking at this, I don't see how it supports the algorithm I've > been using > for years. For that algorithm to successfully migrate PRs across multiple > paths > on a single machine without affecting other

Re: Persistent Reservation API V3

2015-08-29 Thread Christoph Hellwig
On Fri, Aug 28, 2015 at 08:33:24PM -0500, Jeremy Linton wrote: Hello, So, looking at this, I don't see how it supports the algorithm I've been using for years. For that algorithm to successfully migrate PRs across multiple paths on a single machine without affecting other possible

Re: Persistent Reservation API V3

2015-08-28 Thread Jeremy Linton
Hello, So, looking at this, I don't see how it supports the algorithm I've been using for years. For that algorithm to successfully migrate PRs across multiple paths on a single machine without affecting other possible users (who may legitimately have PR'ed the same device) I need PR_IN

Re: Persistent Reservation API V3

2015-08-28 Thread Jeremy Linton
Hello, So, looking at this, I don't see how it supports the algorithm I've been using for years. For that algorithm to successfully migrate PRs across multiple paths on a single machine without affecting other possible users (who may legitimately have PR'ed the same device) I need PR_IN

Persistent Reservation API V3

2015-08-26 Thread Christoph Hellwig
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

Re: Persistent Reservation API V3

2015-08-26 Thread Christoph Hellwig
Meh, looks like the train wifi is too bad to send out a whole patch series. I'll resend once I've arrived.. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at

Persistent Reservation API V3

2015-08-26 Thread Christoph Hellwig
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

Persistent Reservation API V3

2015-08-26 Thread Christoph Hellwig
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

Persistent Reservation API V3

2015-08-26 Thread Christoph Hellwig
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

Persistent Reservation API V3

2015-08-26 Thread Christoph Hellwig
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

Re: Persistent Reservation API V3

2015-08-26 Thread Christoph Hellwig
Meh, looks like the train wifi is too bad to send out a whole patch series. I'll resend once I've arrived.. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at

Persistent Reservation API V3

2015-08-26 Thread Christoph Hellwig
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