mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gérard Roudier" <groudier@free.fr>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Stephan von Krawczynski <skraw@ithnet.com>,
	<linux-kernel@vger.kernel.org>
Subject: Re: Adaptec vs Symbios performance
Date: Sun, 4 Nov 2001 06:23:47 +0100 (CET)	[thread overview]
Message-ID: <20011104060334.Y706-100000@gerard> (raw)
In-Reply-To: <200111040547.fA45ldY64666@aslan.scsiguy.com>



On Sat, 3 Nov 2001, Justin T. Gibbs wrote:

[...]

> >I can see _both_ comparing aic with symbios.
>
> I'm not sure that you would see much of a difference if you set the
> symbios driver to use 253 commands per-device.  I haven't looked at

This is discouraged. :)
Better, IMO, to compare behaviours with realistic queue depths. As you
know, more than 64 for hard disks does not make sense (yet).
Personnaly, I use 64 under FreeBSD and 16 under Linux. Guess why ? :-)

> the sym driver for some time, but last I remember it does not use
> a bottom half handler and handles queue throttling internally.  It

There is no BH in the driver. The stock sym53c8xx even uses scsi_obsolete
that requires more load in interrupt context for command completion.
SYM-2 that comes back from FreeBSD uses the EH threaded stuff that just
queues to a BH on completion. Stephan may want to give SYM-2 a try, IMO.

> may perform less work at interrupt time than the aic7xxx driver if
> locally queued I/O is compiled into a format suitable for controller
> consumption rather than queue the ScsiCmnd structure provided by
> the mid-layer.  The aic7xxx driver has to convert a ScsiCmnd into a
> controller data structure to service an internal queue and this can
> take a bit of time.

The sym* drivers also uses an internal data structure to handle I/Os. The
SCSI script does not know about any O/S specific data structure.

> I would be interresting if there is a disparity in the TPS numbers
> and tag depths in your comparisons.  Higher tag depth usually means
> higher TPS which may also mean less interactive response from the
> system.  All things being equal, I would expect the sym and aic7xxx
> drivers to perform about the same.

Agreed.

  Gérard.


  reply	other threads:[~2001-11-04  8:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200111032318.fA3NIQY62745@aslan.scsiguy.com>
2001-11-04  3:50 ` Stephan von Krawczynski
2001-11-04  5:47   ` Justin T. Gibbs
2001-11-04  5:23     ` Gérard Roudier [this message]
2001-11-04 14:17   ` Stephan von Krawczynski
2001-11-04 18:10     ` Justin T. Gibbs
2001-11-04 18:35     ` Stephan von Krawczynski
2001-11-04 16:31       ` Gérard Roudier
2001-11-04 19:13       ` Justin T. Gibbs
2001-11-04 19:56       ` Stephan von Krawczynski
2001-11-04 20:43         ` Justin T. Gibbs
2001-11-05 12:18           ` Matthias Andree
2001-11-04 19:02     ` Stephan von Krawczynski
2001-11-02 22:42 Google's mm problem - not reproduced on 2.4.13 Ben Smith
2001-11-03 22:53 ` Adaptec vs Symbios performance Stephan von Krawczynski
2001-11-03 23:01   ` arjan

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=20011104060334.Y706-100000@gerard \
    --to=groudier@free.fr \
    --cc=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skraw@ithnet.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

all inboxes | Powered by JetHome®