PR PREEMPT with no reservation at all

Charles Binford Charles.Binford at sun.com
Wed Jul 16 07:00:15 PDT 2003


* From the T10 Reflector (t10 at t10.org), posted by:
* Charles Binford <Charles.Binford at Sun.COM>
*
This is a multi-part message in MIME format.

--Boundary_(ID_hPQh7hXn9UHs6mkmN7TPYg)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

I agree that a preempt should remove registrations regardless of whether
or not a reservation exists.  
 

Charles Binford 
Sun Microsystems 
316.315.0382 x222 

-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Elliott,
Robert (Server Storage)
Sent: Tuesday, July 15, 2003 11:01 PM
To: t10 at t10.org
Subject: PR PREEMPT with no reservation at all



In the PREEMPT flowchart in spc3r05 and earlier, the "Existing
persistent reservation? no" question lead to "Remove registration
pointed to by the service action reservation key."  When All Registrants
was added in spc3r06, the arc was changed to go straight to "Done".

How should PREEMPT and PREEMPT AND ABORT be handled if there is no
persistent reservation at all?  Do nothing (per spc3r05), or go ahead
and remove the specified registrations and (for PREEMPT AND ABORT) abort
the related tasks (per spc3r06+)?

There doesn't seem to be much supporting text for the spc3r06+ figure
except for the first 7 words in 5.5.2.7.4.4: "If there is a persistent
reservation and if the SERVICE ACTION RESERVATION KEY field does not
identify a persistent reservation holder the device server shall perform
a preempt by doing the following in an uninterrupted series of
actions:".  This phrase was added in spc3r13 per 03-094r3 to better
match the (possibly broken) figure 3.

I think the original behavior of "remove registrations (and abort
tasks)" might make more sense. 

See: 
SPC-3 revision 5 section 5.5.3.7.3.1 figure 3 page 69 
SPC-3 revision 14 section 5.5.2.7.4.1 figure 3 page 72 
03-094r3 Yet more persistent reservations fixes 

--- 
Rob Elliott, HP Server Storage 
elliott at hp.com 


--Boundary_(ID_hPQh7hXn9UHs6mkmN7TPYg)
Content-type: text/html; charset=us-ascii
Content-transfer-encoding: 7BIT

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

 Message I agree that a preempt should remove registrations regardless of whether or not a reservation exists.  
 
 Charles Binford 
Sun Microsystems 
316.315.0382 x222 
-----Original Message-----
From: owner-t10 at t10.org [mailto:owner-t10 at t10.org] On Behalf Of Elliott, Robert (Server Storage)
Sent: Tuesday, July 15, 2003 11:01 PM
To: t10 at t10.org
Subject: PR PREEMPT with no reservation at all


 In the PREEMPT flowchart in spc3r05 and earlier, the "Existing persistent reservation? no" question lead to "Remove registration pointed to by the service action reservation key."  When All Registrants was added in spc3r06, the arc was changed to go straight to "Done". How should PREEMPT and PREEMPT AND ABORT be handled if there is no persistent reservation at all?  Do nothing (per spc3r05), or go ahead and remove the specified registrations and (for PREEMPT AND ABORT) abort the related tasks (per spc3r06+)? There doesn't seem to be much supporting text for the spc3r06+ figure except for the first 7 words in 5.5.2.7.4.4: "If there is a persistent reservation and if the SERVICE ACTION RESERVATION KEY field does not identify a persistent reservation holder the device server shall perform a preempt by doing the following in an uninterrupted series of actions:".  This phrase was added in spc3r13 per 03-094r3 to better match the (possibly broken) figure 3. I think the original behavior of "remove registrations (and abort tasks)" might make more sense. See: 
SPC-3 revision 5 section 5.5.3.7.3.1 figure 3 page 69 
SPC-3 revision 14 section 5.5.2.7.4.1 figure 3 page 72 
03-094r3 Yet more persistent reservations fixes --- 
Rob Elliott, HP Server Storage 
elliott at hp.com 

--Boundary_(ID_hPQh7hXn9UHs6mkmN7TPYg)--




More information about the T10 mailing list