From: Jens Axboe <axboe@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Kai Makisara <Kai.Makisara@kolumbus.fi>,
matthew@wil.cx, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] SCSI sym53c8xx_2: bigger transfer limits
Date: Wed, 1 Mar 2006 16:54:02 +0100 [thread overview]
Message-ID: <20060301155401.GA4816@suse.de> (raw)
In-Reply-To: <1141227541.3276.26.camel@mulgrave.il.steeleye.com>
On Wed, Mar 01 2006, James Bottomley wrote:
> On Wed, 2006-03-01 at 16:29 +0100, Jens Axboe wrote:
> > Strictly speaking, the clustering bit is unrelated. I seem to recall
> > Gerard years ago talking about some sym chips that did not like
> > clustering, hence it was disabled.
>
> Yes, I remember that too ... I've never been able to find out which
> chip, though ... the scripts all seem happily coded for variable size sg
> segments.
>
> However, given the new way 2.6 does memory allocations,
> ENABLE_CLUSTERING will probably make quite a difference to the size of
> the sg list ... since we try to allocate contiguous pages, physical
> merging becomes much more of a possibility (I think I last measured it
> at around 30% of all SG tables, as opposed to <1% with the old
> allocation method).
So if we want to enable clustering, it should be done as a separate
patch just in case...
--
Jens Axboe
next prev parent reply other threads:[~2006-03-01 15:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 19:14 [PATCH] SCSI sym53c8xx_2: bigger transfer limits Kai Makisara
2006-02-28 20:41 ` Matthew Wilcox
2006-03-01 15:29 ` Jens Axboe
2006-03-01 15:39 ` James Bottomley
2006-03-01 15:54 ` Jens Axboe [this message]
2006-03-01 16:00 ` Douglas Gilbert
2006-03-01 16:11 ` Jens Axboe
2006-03-01 16:17 ` James Bottomley
2006-03-01 20:34 ` Kai Makisara
2006-03-01 20:43 ` Jens Axboe
2006-03-01 22:24 ` Kai Makisara
2006-03-02 3:57 ` Matthew Wilcox
2006-03-02 7:29 ` Jens Axboe
2006-03-04 8:16 ` Kai Makisara
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=20060301155401.GA4816@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@SteelEye.com \
--cc=Kai.Makisara@kolumbus.fi \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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;
as well as URLs for NNTP newsgroup(s).