From: James Bottomley <James.Bottomley@SteelEye.com>
To: djshetty <dhirajshetty.junk@mailnull.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Some doubts in Persistent Reservation
Date: Fri, 24 Nov 2006 09:02:20 -0600 [thread overview]
Message-ID: <1164380540.2813.2.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <7519006.post@talk.nabble.com>
On Thu, 2006-11-23 at 23:55 -0800, djshetty wrote:
> 1. Is persistent reservation applied on a target port or on a particular
> LUN connected to a target port. The SCOPE of persistent reservation says
> "Entire LOGICAL UNIT", whereas the registration is done for a target PORT.
> Hence the confusion.
For multi-ported devices it's per LUN per port (unless you specify all
target ports).
> 2. Is there any precise use of the PRGeneration key? I guessed it must be
> used for knowing whether any changes have been on the target (with regards
> to persistent reservation) since the previous command executed.
That's the stated use in section 5.6.5.3 of SPC-3, yes.
James
prev parent reply other threads:[~2006-11-24 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 7:55 Some doubts in Persistent Reservation djshetty
2006-11-24 15:02 ` James Bottomley [this message]
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=1164380540.2813.2.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=dhirajshetty.junk@mailnull.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox