From: Mike Christie <michaelc@cs.wisc.edu>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Kai Makisara <Kai.Makisara@kolumbus.fi>, linux-scsi@vger.kernel.org
Subject: Re: use_clustering again (was Re: SCSI tape block size)
Date: Thu, 28 Sep 2006 15:50:45 -0400 [thread overview]
Message-ID: <451C2795.8040509@cs.wisc.edu> (raw)
In-Reply-To: <Pine.LNX.4.60.0609282211560.3268@poirot.grange>
Guennadi Liakhovetski wrote:
> On Thu, 28 Sep 2006, Kai Makisara wrote:
>
>> The limits come from the block subsystem that all scsi devices use
>> nowadays. It is a rather long story but can be found from linux-scsi
>> archives, e.g.,
>> http://marc.theaimsgroup.com/?l=linux-scsi&m=114147170831847&w=2
>
> Yes, already found the 2 later threads - one on lkml and one on scsi. I
> did look at them briefly back then, but, probably, too briefly.
>
> One of the settings - enable_clustering
If you are just trying to get to 1MB, then instead of enabling
clustering we could also increase the defaul SCSI_MAX_PHYS_SEGMENTS. It
is 128 now, but there is a compile option to set it it up to 256.
Well, actually I think that gets a little short because SG_ALL is only
255. Why is SG_ALL 255, but you can set SCSI_MAX_PHYS_SEGMENTS to 256?
next prev parent reply other threads:[~2006-09-28 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200609241605.32327.johna@onevista.com>
2006-09-27 21:32 ` SCSI tape block size Guennadi Liakhovetski
2006-09-28 14:34 ` Michael Reed
2006-09-28 19:47 ` Kai Makisara
2006-09-28 20:41 ` use_clustering again (was Re: SCSI tape block size) Guennadi Liakhovetski
2006-09-28 19:50 ` Mike Christie [this message]
2006-09-28 21:36 ` use_clustering again Martin K. Petersen
2006-09-30 20:52 ` SCSI tape block size Guennadi Liakhovetski
2006-10-01 10:42 ` Kai Makisara
2006-10-01 17:05 ` Guennadi Liakhovetski
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=451C2795.8040509@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=Kai.Makisara@kolumbus.fi \
--cc=g.liakhovetski@gmx.de \
--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.