mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: sai narasimhamurthy <sai_narasi@yahoo.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
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, 17 Apr 2005 23:17:23 -0700 (PDT)	[thread overview]
Message-ID: <20050418061723.49716.qmail@web54105.mail.yahoo.com> (raw)
In-Reply-To: 6667

Hi , 
I tried working on scsi_malloc to increase burst size
, but to no avail ..all I got was hanged system every
time I started data transfers! 
Has anyone worked on scsi_malloc , I am still trying
to figure out what changes were made in 2.6 to
overcome this problem of limited bursts. 

Any pointers are very greatly welcome...I have never
worked on this part of the code before .


Sai










--- "Randy.Dunlap" <rddunlap@osdl.org> wrote:
> 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
> -
> 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
> 


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/ 

             reply	other threads:[~2005-04-18  6:17 UTC|newest]

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

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=20050418061723.49716.qmail@web54105.mail.yahoo.com \
    --to=sai_narasi@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rddunlap@osdl.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

all inboxes | Powered by JetHome®