All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Jens Axboe <axboe@suse.de>
Cc: dougg@torque.net, Brian King <brking@us.ibm.com>,
	dgilbert@interlog.com,
	SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] sg block layer tcqing fix
Date: 06 Jan 2004 09:30:17 -0600	[thread overview]
Message-ID: <1073403019.2047.10.camel@mulgrave> (raw)
In-Reply-To: <20040106152215.GD3483@suse.de>

On Tue, 2004-01-06 at 09:22, Jens Axboe wrote:
> On Tue, Jan 06 2004, James Bottomley wrote:
> > +	/* unlikely because the tag was usually ended earlier
> > +	 *
> > +	 * NOTE: the lock should be held while checking the
> > +	 * flag.  However, any race here requiring the lock
> > +	 * would be a gross error. */
> 
> I don't agree with this comment - why would you need to have the queue
> lock to check req->flags?

Because the usual scsi method of doing this is:

	spin_lock_irqsave(q->queue_lock, flags);
	if (blk_rq_tagged(req))
		blk_queue_end_tag(q, req);
	spin_unlock_irqrestore(q->queue_lock, flags);

which was done because the REQ_QUEUE flag is altered by the
blk_queue_end_tag(), so I wanted to note that I'd done this one
differently deliberately.

On the other hand, I don't see the possibility of a legal race to do
this in any of our other block tag ending code either...perhaps I should
just convert them all to this form.

James


  reply	other threads:[~2004-01-06 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-29 20:29 [PATCH] sg block layer tcqing fix Brian King
2004-01-06  5:06 ` Douglas Gilbert
2004-01-06 11:46   ` Willem Riede
2004-01-06 15:14   ` James Bottomley
2004-01-06 15:22     ` Jens Axboe
2004-01-06 15:30       ` James Bottomley [this message]
2004-01-06 15:37         ` Jens Axboe

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=1073403019.2047.10.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=axboe@suse.de \
    --cc=brking@us.ibm.com \
    --cc=dgilbert@interlog.com \
    --cc=dougg@torque.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.