From: Christof Schmitt <christof.schmitt@de.ibm.com>
To: Julia Lawall <julia@diku.dk>
Cc: "James E.J. Bottomley" <James.Bottomley@suse.de>,
linux-scsi@vger.kernel.org, joe@perches.com
Subject: Re: question about drivers/scsi/scsi_transport_fc.c
Date: Thu, 2 Sep 2010 12:53:26 +0200 [thread overview]
Message-ID: <20100902105326.GA4097@schmichrtp.mainz.de.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1008281908150.13508@ask.diku.dk>
On Sat, Aug 28, 2010 at 07:11:12PM +0200, Julia Lawall wrote:
> The function fc_bsg_goose_queue in the file drivers/scsi/scsi_transport_fc.c
> contains the following code:
>
> flagset = test_bit(QUEUE_FLAG_REENTER, &rport->rqst_q->queue_flags) &&
> !test_bit(QUEUE_FLAG_REENTER, &rport->rqst_q->queue_flags);
>
> I have the impression that this is always 0. QUEUE_FLAG_REENTER is
> defined with quite a lot of other constants, so I don't really have a
> guess as to what was intended.
I just came across the code in scsi_run_queue in
drivers/scsi/scsi_lib.c. It looks like the check of QUEUE_FLAG_REENTER
in fc_bsg_goose_queue is modeled after the check in scsi_run_queue.
The check in scsi_run_queue has been introduced with this commit,
maybe this helps understanding the code:
commit 04846f25920d4b05d6040c531cc601049260db52
Author: Andreas Herrmann <aherrman@de.ibm.com>
Date: Wed Aug 9 17:31:16 2006 +0200
[SCSI] limit recursion when flushing shost->starved_list
--
Christof
next prev parent reply other threads:[~2010-09-02 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 17:11 question about drivers/scsi/scsi_transport_fc.c Julia Lawall
2010-09-02 10:53 ` Christof Schmitt [this message]
2010-09-02 13:39 ` Hannes Reinecke
2010-09-02 14:28 ` Christof Schmitt
2010-09-02 15:01 ` [PATCH] scsi: Remove QUEUE_FLAG_REENTER from SCSI code Christof Schmitt
2010-09-27 7:58 ` James Bottomley
2010-10-04 13:47 ` Christof Schmitt
2010-10-05 9:00 ` [PATCH v2] " Christof Schmitt
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=20100902105326.GA4097@schmichrtp.mainz.de.ibm.com \
--to=christof.schmitt@de.ibm.com \
--cc=James.Bottomley@suse.de \
--cc=joe@perches.com \
--cc=julia@diku.dk \
--cc=linux-scsi@vger.kernel.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