mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] add sysfs to dynamically control blk request tag maintenance
Date: Fri, 7 Oct 2005 09:41:39 +0200	[thread overview]
Message-ID: <20051007074138.GP2889@suse.de> (raw)
In-Reply-To: <B05667366EE6204181EABE9C1B1C0EB5086AEC2E@scsmsx401.amr.corp.intel.com>

On Fri, Oct 07 2005, Chen, Kenneth W wrote:
> Jens Axboe wrote on Friday, October 07, 2005 12:24 AM
> > I don't understand the need for this patch - the generic tagging is
> only
> > used if the SCSI LLD indicated it wanted it by issuing a
> > scsi_activate_tcq(). So blk_queue_start_tag() is only called if the
> LLD
> > already did a scsi_activate_tcq(), and blk_queue_end_tag() is only
> > called if the rq is block layer tagged. blk_queue_find_tag() is only
> > used with direct use of scsi_find_tag(), a function that should (and
> is)
> > only usable by users of the generic tagging already.
> > 
> 
> You beat me by a couple of minutes.  I was about to say that the culprit
> is in the qla2x00 driver where it unnecessarily activated generic blk
> tag queuing by calling scsi_activate_tcq() and it never uses tag.
> 
> > So please, a description of what problem you are trying to solve would
> > be appreciated :-)
> 
> It starts out with scsi_end_request being a fairly hot function in the
> execution profile, then I noticed blk_queue_start/end_tag() are being
> called but no actual consumer of using the tag.  I'm trying to find a
> way to avoid making these blk_queue_start/end_tag calls.  I got the
> answer
> now. The proper way is to fix it in the scsi LLDD.  Scratch this patch,
> new patch to follow :-)

Ok that makes more sense! But it's a little worrying that
blk_queue_end_tag() would show up as hot in the profile, it is actually
quite lean.

-- 
Jens Axboe


  reply	other threads:[~2005-10-07  7:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07  7:35 Chen, Kenneth W
2005-10-07  7:41 ` Jens Axboe [this message]
2005-10-07  7:50   ` Arjan van de Ven
2005-10-07  8:06     ` Jens Axboe
2005-10-07  8:25       ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2005-10-07  8:13 Chen, Kenneth W
2005-10-07 16:57 ` Andrew Vasquez
2005-10-07 18:17   ` Jens Axboe
2005-10-07  8:04 Chen, Kenneth W
2005-10-07  7:52 Chen, Kenneth W
2005-10-07  8:07 ` Jens Axboe
2005-10-07  2:46 Chen, Kenneth W
2005-10-07  7:23 ` 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=20051007074138.GP2889@suse.de \
    --to=axboe@suse.de \
    --cc=kenneth.w.chen@intel.com \
    --cc=linux-kernel@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

Powered by JetHome