From: Luben Tuikov <luben@splentec.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] 3/7 consolidate single_lun code
Date: Tue, 25 Mar 2003 15:50:54 -0500 [thread overview]
Message-ID: <3E80C12E.2000405@splentec.com> (raw)
In-Reply-To: 20030324180247.B15047@beaverton.ibm.com
Patrick Mansfield wrote:
> Consolidate scsi single_lun code.
>
> diff -purN -X /home/patman/dontdiff put_cmd-25/drivers/scsi/scsi_lib.c lun-single-25/drivers/scsi/scsi_lib.c
> --- put_cmd-25/drivers/scsi/scsi_lib.c Mon Mar 24 12:14:51 2003
> +++ lun-single-25/drivers/scsi/scsi_lib.c Mon Mar 24 12:14:55 2003
> @@ -323,6 +323,49 @@ void scsi_setup_cmd_retry(struct scsi_cm
> }
>
> /*
> + * Called for single_lun devices. The target associated with current_sdev can
> + * only handle one active command at a time. Scan through all of the luns
> + * on the same target as current_sdev, return 1 if any are active.
> + */
> +static int scsi_single_lun_check(struct scsi_device *current_sdev)
This is such a general name, that it does not mean anything.
What kind of ``check'' is this?
Why not like this:
/**
* scsi_target_ok2queue: return non-zero if it is ok to queue
* to this target, else 0.
*/
<< but a nicely formatted comment>>
static int scsi_target_ok2queue(struct scsi_target *target)
{
if (!target->single_lu)
return 1;
for all devices of the target
if an LU is active
return 0;
return 1;
}
That is, 0 is returned when there is NO error code.
Since this function does NOT return error codes, but performes
a LOGICAL nature test, you'd return 1 and 0, so that this makes sense:
if (scsi_target_ok2queue(target)) {
/* we're ok to queue, go! */
} else {
/* no we're not ok to queue */
}
and the negation:
if (!scsi_target_ok2queue(target)) {
...
I'd rather have it named int scsi_target_canqueue(), but there
might be some confusion with the can_queue struct member.
> +{
> + struct scsi_device *sdev;
> +
> + list_for_each_entry(sdev, ¤t_sdev->same_target_siblings,
> + same_target_siblings)
> + if (sdev->device_busy)
> + return 1;
> + return 0;
> +}
> +
> +/*
> + * Called for single_lun devices on IO completion. If no requests
> + * outstanding for current_sdev, call __blk_run_queue for the next
> + * scsi_device on the same target that has requests.
> + *
> + * Called with queue_lock held.
> + */
> +static void scsi_single_lun_run(struct scsi_device *current_sdev,
> + struct request_queue *q)
This will be incorporated by default by the starved_devs list
priority queue.
I.e. you should try not to have a partucular function for this but
arrange the infrastructure in such a way that this is handled
by default (via the infrastructure itself).
> +{
> + struct scsi_device *sdev;
> + struct Scsi_Host *shost;
> +
> + shost = current_sdev->host;
> + if (blk_queue_empty(q) && current_sdev->device_busy == 0 &&
> + !shost->host_blocked && !shost->host_self_blocked &&
> + !((shost->can_queue > 0) &&
> + (shost->host_busy >= shost->can_queue)))
> + list_for_each_entry(sdev, ¤t_sdev->same_target_siblings,
> + same_target_siblings)
> + if (!sdev->device_blocked &&
> + !blk_queue_empty(sdev->request_queue)) {
> + __blk_run_queue(sdev->request_queue);
> + break;
> + }
> +}
> +
> +/*
> * Function: scsi_queue_next_request()
> *
> * Purpose: Handle post-processing of completed commands.
> @@ -390,29 +433,11 @@ void scsi_queue_next_request(request_que
> }
>
> sdev = q->queuedata;
> - shost = sdev->host;
>
> - /*
> - * If this is a single-lun device, and we are currently finished
> - * with this device, then see if we need to get another device
> - * started. FIXME(eric) - if this function gets too cluttered
> - * with special case code, then spin off separate versions and
> - * use function pointers to pick the right one.
> - */
> - if (sdev->single_lun && blk_queue_empty(q) && sdev->device_busy ==0 &&
> - !shost->host_blocked && !shost->host_self_blocked &&
> - !((shost->can_queue > 0) && (shost->host_busy >=
> - shost->can_queue))) {
> - list_for_each_entry(sdev2, &sdev->same_target_siblings,
> - same_target_siblings) {
> - if (!sdev2->device_blocked &&
> - !blk_queue_empty(sdev2->request_queue)) {
> - __blk_run_queue(sdev2->request_queue);
> - break;
> - }
> - }
> - }
> + if (sdev->single_lun)
> + scsi_single_lun_run(sdev, q);
>
> + shost = sdev->host;
> while (!list_empty(&shost->starved_list) &&
> !shost->host_blocked && !shost->host_self_blocked &&
> !((shost->can_queue > 0) &&
> @@ -917,22 +942,6 @@ static int scsi_init_io(struct scsi_cmnd
> return BLKPREP_KILL;
> }
>
> -/*
> - * The target associated with myself can only handle one active command at
> - * a time. Scan through all of the luns on the same target as myself,
> - * return 1 if any are active.
> - */
> -static int check_all_luns(struct scsi_device *myself)
> -{
> - struct scsi_device *sdev;
> -
> - list_for_each_entry(sdev, &myself->same_target_siblings,
> - same_target_siblings)
> - if (sdev->device_busy)
> - return 1;
> - return 0;
> -}
> -
> static int scsi_prep_fn(struct request_queue *q, struct request *req)
> {
> struct Scsi_Device_Template *sdt;
> @@ -1077,9 +1086,6 @@ static void scsi_request_fn(request_queu
> if (sdev->device_busy >= sdev->queue_depth)
> break;
>
> - if (sdev->single_lun && check_all_luns(sdev))
> - break;
> -
> if (shost->host_busy == 0 && shost->host_blocked) {
> /* unblock after host_blocked iterates to zero */
> if (--shost->host_blocked == 0) {
> @@ -1120,6 +1126,9 @@ static void scsi_request_fn(request_queu
> break;
> }
>
> + if (sdev->single_lun && scsi_single_lun_check(sdev))
> + break;
> +
> /*
> * If we couldn't find a request that could be queued, then we
> * can also quit.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Luben Tuikov, Senior Software Engineer, Splentec Ltd.
Bus: +1-905-707-1954x112, 9-5 EDT. Fax: +1-905-707-1974.
next prev parent reply other threads:[~2003-03-25 20:50 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 1:53 [PATCH] 0/7 per scsi_device queue lock patches Patrick Mansfield
2003-03-25 1:54 ` [PATCH] 1/7 starved changes - use a list_head for starved queue's Patrick Mansfield
2003-03-25 2:02 ` [PATCH] 2/7 add missing scsi_queue_next_request calls Patrick Mansfield
2003-03-25 2:02 ` [PATCH] 3/7 consolidate single_lun code Patrick Mansfield
2003-03-25 2:03 ` [PATCH] 4/7 cleanup/consolidate code in scsi_request_fn Patrick Mansfield
2003-03-25 2:03 ` [PATCH] 5/7 alloc a request_queue on each scsi_alloc_sdev call Patrick Mansfield
2003-03-25 2:03 ` [PATCH] 6/7 add and use a per-scsi_device queue_lock Patrick Mansfield
2003-03-25 2:04 ` [PATCH] 7/7 fix single_lun code for " Patrick Mansfield
2003-03-25 21:23 ` Luben Tuikov
2003-03-26 21:47 ` Patrick Mansfield
2003-03-26 22:12 ` Luben Tuikov
2003-03-25 21:03 ` [PATCH] 6/7 add and use a " Luben Tuikov
2003-03-26 21:33 ` Patrick Mansfield
2003-03-25 21:20 ` James Bottomley
2003-03-26 2:01 ` Patrick Mansfield
2003-03-27 16:09 ` James Bottomley
2003-03-28 0:30 ` Patrick Mansfield
2003-03-25 7:12 ` [PATCH] 5/7 alloc a request_queue on each scsi_alloc_sdev call Christoph Hellwig
2003-03-25 7:18 ` Jens Axboe
2003-03-25 21:32 ` [PATCH] 4/7 cleanup/consolidate code in scsi_request_fn Luben Tuikov
2003-03-26 0:58 ` Patrick Mansfield
2003-03-26 17:07 ` Luben Tuikov
2003-03-26 17:13 ` Patrick Mansfield
2003-03-26 17:25 ` Luben Tuikov
2003-03-25 20:36 ` [PATCH] 3/7 consolidate single_lun code Luben Tuikov
2003-03-26 19:11 ` Patrick Mansfield
2003-03-26 22:05 ` Luben Tuikov
2003-03-27 22:43 ` Patrick Mansfield
2003-03-28 15:09 ` Luben Tuikov
2003-03-28 20:06 ` Patrick Mansfield
2003-03-25 20:50 ` Luben Tuikov [this message]
2003-03-25 19:41 ` [PATCH] 2/7 add missing scsi_queue_next_request calls Luben Tuikov
2003-03-25 19:39 ` [PATCH] 1/7 starved changes - use a list_head for starved queue's Luben Tuikov
2003-03-27 16:14 ` [PATCH] 0/7 per scsi_device queue lock patches 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=3E80C12E.2000405@splentec.com \
--to=luben@splentec.com \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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