Boaz Harrosh wrote:
Douglas Gilbert wrote:
or (adding "_TA_" for task attribute):
enum {
BSG_TA_DEFAULT = 0, // lk 2.4, 2.6 series: head of queue
BSG_TA_HEAD_OF_Q = 0x1000,
BSG_TA_SIMPLE,
BSG_TA_ORDERED,
BSG_TA_ACA,
....
BSG_TA_HEAD_OF_Q I understand that's like today. What are the meaning
of the other values? Anyway I only have 2 values to implement I don't want
to add more values then I use, and have to comment NOT SUPPORTED next
to them. When used I can add them later.
Please Note that I was asking about the at_head=0/1 of the blk_execute_rq_xxx
calls. This means that it is not transport specific at all, it is a Boolean behavior
common to all transports, governed by the request submission layer.
If task_attribute is something related to SAM-4 then surly that is not it, because
I'm looking for a flag that is independent of scsi. If later I will need that SAM-4
thing it will be taken.
I would prefer using the request_attr field.
Tomo, what do you think?
Doug Gilbert
And please, you never explained, what is "request_priority" for?
What was your original intention?
Boaz,
As my comment indicates "request_priority" is "task priority" in
SCSI. I should have added "... in SAM-3" because the good folks
at t10 changed that to "command priority" in SAM-4 (sam4r14.pdf
section 8.7). [I didn't like the term "task ..." either which is
one reason why I used "request ...".]
So the "queue" that I'm talking about is the one on the device
(target or LU, take your pick). A SCSI pass-through wants the
thinnest possible layer between itself and the SCSI initiator,
so in that context I view a queue in the scsi mid-level or
a LLD as evil.
Note also that several SCSI commands have an implicit "head of
queue" attribute (e.g. INQUIRY and REPORT LUNS) within the
device.
Doug Gilbert
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
