public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: Li Liu <li.liu0637@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Slower write performance in RHEL6
Date: Tue, 26 Jul 2011 07:38:20 -0400	[thread overview]
Message-ID: <4E2EA72C.7030109@redhat.com> (raw)
In-Reply-To: <CAMYVA_nrqA_GFnRXFFUJp=NYfYLy7z6gC7Tur8EQmgOEKvqf4Q@mail.gmail.com>

On 07/26/2011 07:22 AM, Li Liu wrote:
> Dear all,
>
>      In RHEL6(linux-2.6.32-71.el6), I added some codes in
> scsi_softirq_done to check the result of execute scsi commands:
> WRITE_6, WRITE_10, WRITE_12, WRITE_16 when I executed "dd if=/dev/zero
> of=/dev/xda bs=64k count=10000". I found a lot of write error messages
> in scsi_softirq_done, the disposition(variable) was ADD_TO_MLQUEUE and
> the speed was 78MB/s.
>      Then I changed MPT_SCSI_CMD_PER_DEV_HIGH from 64 to 32 in
> mptscsih_change_queue_depth, the speed was 140MB/s and none error
> messages.
>      * /dev/xda is a scsi disk.
>      * the scsi host is LSI1064E.
>      * MPT_SCSI_CMD_PER_DEV_HIGH will be assigned to blk_queue_tag->max_depth.
>
>      My questions are:
>      Is the TCQ depth limited by hard disk, how can I get the limited?
>      Why the speed was drop to 78MB/s when MPT_SCSI_CMD_PER_DEV_HIGH was 64?
>      Could I change MPT_SCSI_CMD_PER_DEV_HIGH to 32 or 16 or 8, Will it
> cause any problem?
>
>      Thanks for any ideas.
>
> Thanks,
> Alex Liu

When you have a vendor specific issues, it is probably best to raise a ticket 
with the vendor's support organization....

Thanks!

Ric



      reply	other threads:[~2011-07-26 11:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 11:22 Slower write performance in RHEL6 Li Liu
2011-07-26 11:38 ` Ric Wheeler [this message]

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=4E2EA72C.7030109@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=li.liu0637@gmail.com \
    --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