From: djshetty <dhirajshetty.junk@mailnull.com>
To: linux-scsi@vger.kernel.org
Subject: Some doubts in Persistent Reservation
Date: Thu, 23 Nov 2006 23:55:16 -0800 (PST) [thread overview]
Message-ID: <7519006.post@talk.nabble.com> (raw)
Hi,
I have been trying to understand PERSISTENT RESERVATION as per SCSI SPC-3
standards. I had the following two doubts:
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.
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.
Regards,
Dhiraj.
--
View this message in context: http://www.nabble.com/Some-doubts-in-Persistent-Reservation-tf2696285.html#a7519006
Sent from the linux-scsi mailing list archive at Nabble.com.
next reply other threads:[~2006-11-24 7:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 7:55 djshetty [this message]
2006-11-24 15:02 ` Some doubts in Persistent Reservation James Bottomley
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=7519006.post@talk.nabble.com \
--to=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