Skip to contentSkip to conversation

question on SDEV_BLOCK vs. SDEV_QUIESCE

DISCUSSION Oliver Neukum 2 participants 3 messages Sep 25, 2007 SCSI

lore
Share & tools
lore
#0 lore raw

Hi,

what is the difference between these states? What function should I call to block a device in order to securely flush the caches?

Regards
Oliver

#1 lore raw
Quoted 5 lines · Oliver Neukum

Hi,

what is the difference between these states? What function should I call to block a device in order to securely flush the caches?

SDEV_BLOCK blocks _any_ commands from the midlayer; eg. if the LLDD is doing some internal recovery.
SDEV_QUIESCE only blocks 'normal' data commands; others (like control commands) can still get through.

So for flushing you should use SDEV_QUIESCE.

Cheers,

Hannes

Signature · 8 lines
Dr. Hannes Reinecke		      zSeries & Storage
[email protected]			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
#2 lore raw

Am Dienstag 25 September 2007 schrieb Hannes Reinecke:

Quoted 6 lines
Quoted 5 lines · Oliver Neukum

Hi,

what is the difference between these states? What function should I call to block a device in order to securely flush the caches?

Quoted 6 lines

SDEV_BLOCK blocks _any_ commands from the midlayer; eg. if the LLDD is doing some internal recovery.
SDEV_QUIESCE only blocks 'normal' data commands; others (like control commands) can still get through.

So for flushing you should use SDEV_QUIESCE.

Thank you, that's very helpful.

Regards
Oliver