public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Lord <lord@xfs.org>
To: linux-scsi@vger.kernel.org, aradford@gmail.com
Subject: 3ware driver maximum request size
Date: Thu, 17 Aug 2006 10:13:03 -0500	[thread overview]
Message-ID: <44E4877F.2070708@xfs.org> (raw)


Does anyone know why the 3ware driver caps I/O at 128K bytes per scsi
request? The driver defines a scatter gather array which will always
cope with at least twice this.

I am running with the TW_MAX_SECTORS constant at 512 and getting
256K I/Os to a 6+1 raid5 lun on a 9550SX. By my calculations this
does not exceed the defined sizes of the scatter gather arrays for
this type of device (but would I guess for the escalade variant
in the code).

I know nothing about the hardware itself, but if this works it seems
like a worthwhile change for the newer devices.

Thanks

   Steve Lord


             reply	other threads:[~2006-08-17 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-17 15:13 Steve Lord [this message]
2006-08-18 18:46 ` 3ware driver maximum request size adam radford
2006-08-18 19:08   ` Steve Lord

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=44E4877F.2070708@xfs.org \
    --to=lord@xfs.org \
    --cc=aradford@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