public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: sai narasimhamurthy <sai_narasi@yahoo.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: increasing scsi_max_sg / max_segments for scsi writes/reads
Date: Sun, 10 Apr 2005 18:41:56 -0700	[thread overview]
Message-ID: <20050410184156.3014a2ea.rddunlap@osdl.org> (raw)
In-Reply-To: <20050410023552.2545.qmail@web54101.mail.yahoo.com>

On Sat, 9 Apr 2005 19:35:52 -0700 (PDT) sai narasimhamurthy wrote:

| Hi, 
| I had posted a question on increasing the scsi
| read/write sectors  per command. I figured out some of
| the things, but many questions still exist. 
| 
| I was wondering why the maximum writes I could get
| from a single scsi write command could never exceed
| 204 
| 4096B  segments . I traced it to :  
| 
| static const int scsi_max_sg = PAGE_SIZE /
| sizeof(struct scatterlist)
| 
| in scsi_merge.c .(which amounts to 204)  
| 
| Is this the limit of the maximum blocks we can
| read/write through a single scsi command, atleast for
| the given kernel (2.4.29) ? How can I increase
| it??????
| 
| I am on a P3 Dell poweredgde 2400 . 

Did you read the comment immediately above that
calculation?

/*
 * scsi_malloc() can only dish out items of PAGE_SIZE or less, so we cannot
 * build a request that requires an sg table allocation of more than that.
 */

so scsi_malloc() would need some reworking to handle more.

OTOH, it appears that this is all removed in 2.6.10++, so moving to
2.6.recent is probably your best choice.

---
~Randy

  reply	other threads:[~2005-04-11  1:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10  2:35 increasing scsi_max_sg / max_segments for scsi writes/reads sai narasimhamurthy
2005-04-11  1:41 ` Randy.Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-04-18  6:17 sai narasimhamurthy
2005-04-18 14:12 ` James Bottomley

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=20050410184156.3014a2ea.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sai_narasi@yahoo.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