public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: john clyne <clyne@ucar.edu>
To: linux-scsi@vger.kernel.org
Subject: Re: IO transfer limits
Date: Wed, 10 Jan 2007 15:07:01 -0800 (PST)	[thread overview]
Message-ID: <8268682.post@talk.nabble.com> (raw)
In-Reply-To: <45A53290.1060400@torque.net>


So given that the HBA max_sectors_kb looks sufficiently large, my
interpretation of your article is the next place I need to look is at
ajusting SCSI_MAX_PHYS_SEGMENTS. Sounds like i can only increase this to
256. Does that than give me a max transfer size of 256 * page_size (4k) =
1MB? Is 1MB the limit or am I missing something?

thanks - jc


Douglas Gilbert wrote:
> 
> john clyne wrote:
>> Can anyone give me some guidance on where in the IO stack I might be
>> running
>> into a 512KB limit on IO transfer sizes to an external FC device? I've
>> checked IO scheduler parameter
>> (/sys/block/<dev>/queue/{max_sectors_kb,max_hw_sectors_kb}. Both are set
>> to
>> 32767. I'm using Qlogic HBAs (qla2312), but I don't see any relevent
>> parameters. I'm running RHEL 4.0 with a 2.6.9-34 kernel. Any pointers
>> would
>> be greatly appreciated.
> 
> John,
> I discuss the subject in this page:
>    http://www.torque.net/sg/sg_io.html
> in the section titled:
> Maximum transfer size per command
> 
> Mike C. has given you the answer for the block device
> interface (e.g. via /dev/sda); you should be able
> to do about 8 times better via the scsi generic
> interface (e.g. /dev/sg0).
> 
> Doug Gilbert
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

-- 
View this message in context: http://www.nabble.com/IO-transfer-limits-tf2953389.html#a8268682
Sent from the linux-scsi mailing list archive at Nabble.com.


  reply	other threads:[~2007-01-10 23:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-10 16:16 IO transfer limits john clyne
2007-01-10 17:40 ` Mike Christie
2007-01-10 23:47   ` john clyne
2007-01-11  1:15     ` Douglas Gilbert
2007-01-11 16:13       ` Stefan Richter
2007-01-11 21:50         ` Douglas Gilbert
2007-01-12  0:54           ` Stefan Richter
2007-01-12 22:27   ` john clyne
2007-01-10 18:38 ` Douglas Gilbert
2007-01-10 23:07   ` john clyne [this message]
2007-01-11 18:23     ` James Bottomley
2007-01-11 19:48       ` john clyne
2007-01-12  1:17         ` James Bottomley
2007-01-11 19:23   ` no utility / method to show association between host bus adapter and non-sg BLOCK devices Thayne Harmon
2007-01-11 20:15     ` Douglas Gilbert
     [not found]       ` <45AE22E0.DB3A.00B8.0@novell.com>
2007-01-17 21:04         ` no utility / method to show association between HBA & non-sg BLOCK (scsi) devices - register_blkdev() Douglas Gilbert
2007-01-17 22:06           ` Andrew Patterson

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=8268682.post@talk.nabble.com \
    --to=clyne@ucar.edu \
    --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