public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: dgilbert@interlog.com
Cc: Douglas Gilbert <dougg@torque.net>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	open-osd mailing-list <osd-dev@open-osd.org>
Subject: Re: [Q] In sg_io_v4 what to use as flag for "queue at_head"
Date: Tue, 20 Jan 2009 09:05:41 +0200	[thread overview]
Message-ID: <497577C5.6080604@panasas.com> (raw)
In-Reply-To: <4974BBC5.3080001@interlog.com>

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?

Thanks
Boaz

  parent reply	other threads:[~2009-01-20  7:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19 11:18 [Q] In sg_io_v4 what to use as flag for "queue at_head" Boaz Harrosh
2009-01-19 17:43 ` Douglas Gilbert
2009-01-19 18:24   ` Douglas Gilbert
2009-01-20  7:05   ` Boaz Harrosh [this message]
2009-01-20 19:27     ` Douglas Gilbert
2009-01-21  5:31     ` FUJITA Tomonori
2009-01-21  5:31   ` FUJITA Tomonori
2009-01-21  8:12     ` Boaz Harrosh

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=497577C5.6080604@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=dgilbert@interlog.com \
    --cc=dougg@torque.net \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-scsi@vger.kernel.org \
    --cc=osd-dev@open-osd.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