From: john clyne <clyne@ucar.edu>
To: linux-scsi@vger.kernel.org
Subject: Re: IO transfer limits
Date: Thu, 11 Jan 2007 11:48:41 -0800 (PST) [thread overview]
Message-ID: <8284792.post@talk.nabble.com> (raw)
In-Reply-To: <1168539824.2983.11.camel@mulgrave.il.steeleye.com>
So what's the best course of action for increasing the 512kb IO transfer size
limit, changing SCSI_MAX_PHYS_SEGMENTS (currently 128 and apparently can be
set no greater than 256), or increasing the page size? Or is there another
option.
thanks - jc
James Bottomley wrote:
>
> On Wed, 2007-01-10 at 15:07 -0800, john clyne wrote:
>> 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?
>
> Well ... that's not the maximum possible ... just the maximum number of
> SG elements. If the buffer is completely fragmented in physical memory,
> then it will be 1MB ... however, linux does a reasonable job of getting
> physically contiguous pages into a large memory allocation, so you could
> get transfers that are larger than the 1MB limit by quite a way. And,
> of course, any system that has a larger page size or uses an iommu will
> go over this 1MB as well.
>
> Jmaes
>
>
> -
> 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#a8284792
Sent from the linux-scsi mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-01-11 19:48 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
2007-01-11 18:23 ` James Bottomley
2007-01-11 19:48 ` john clyne [this message]
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=8284792.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.