public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: scameron@beardog.cce.hp.com
To: linux-scsi@vger.kernel.org
Cc: mike.miller@hp.com, james.bottomley@hansenpartnership.com,
	scameron@beardog.cce.hp.com
Subject: 16 commands per lun limitation bug?
Date: Wed, 10 Feb 2010 14:19:16 -0600	[thread overview]
Message-ID: <20100210201916.GK11649@beardog.cce.hp.com> (raw)


We have seen the amount of commands per lun that are sent to 
low level scsi driver limited to 16 commands per lun,
(seemingly artificially, well below our can_queue and
cmd_per_lun limits of 1020)

2.6.29 does not exhibit this bad behavior.
2.6.30, 2.6.31, 2.6.32 (2.6.32.1 through 2.6.32.8) do exhibit this bad behavior
2.6.31-rc1 does not exhibit this bad behavior

Testing was done with fio with this config file:

[global]
description=4096 byte random reads - ${CONFIG}
readwrite=randread
blocksize=4K
ioengine=libaio
softrandommap=1
direct=1
runtime=2000
time_based
#ramp_time=10
thread
filename=/dev/sdb

[iodepth=128]
stonewall
iodepth=128

When the problem is present, we only see 16 commands per lun, when
not present, we see 128 commands per lun.

Anybody else seen this problem?  Anybody know what caused the
brokeness between 2.6.29 and 2.6.30, or what fixed this between
2.6.32 and 2.6.33-rc1?

Hard for me to do a git bisect as the only hardware I have capable
of exercising the test case is Smart Array, and hpsa didn't go in
until 2.6.33-rc1.   Would like to know if other hardware/drivers
encounter this problem as well.

-- steve 



             reply	other threads:[~2010-02-10 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 20:19 scameron [this message]
2010-02-10 21:59 ` 16 commands per lun limitation bug? James Bottomley
2010-02-10 22:19   ` Miller, Mike (OS Dev)
2010-02-10 22:22     ` James Bottomley
2010-02-11  2:27       ` scameron

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=20100210201916.GK11649@beardog.cce.hp.com \
    --to=scameron@beardog.cce.hp.com \
    --cc=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.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