public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Giammarco <mgiammarco@virgilio.it>
To: Fabien Salvi <fabien@cri74.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Bad fibre channel performance: need howto
Date: Mon, 24 Nov 2003 12:30:45 +0100	[thread overview]
Message-ID: <1069673445.1231.18.camel@cala> (raw)
In-Reply-To: <3FC1E393.4090907@cri74.org>

Il lun, 2003-11-24 alle 11:55, Fabien Salvi ha scritto:

> Hello Mario,
> 


> If you want, I can send you an archive of the howto.
> I've downloaded it a long time ago, before sistina removed it from their 
> server.
> 
> But, it's true, it's a bit old

Yes send it to me please. I like to read all.

> About your problem, I am not sure it's really because of FibreChannel.
> There are a lot of differences between theorical values and real ones.
> Which tool are you using for the benchmark ?

I know but usually the "sequential read" is the easiest test to discover
if there are problems.

I have used hdparm and sg3 tools to do a quick sequential read test.
On ide world if hdparm tells me that I have  sequential transfer rate
lower than shown on web reviews it means that I have to tweak dma, etc.
and usually after tweaking I get performance promised.

Here there is little to tweak and I then discovered with a serious test
(tiobench) that write performance is also worse.

I suppose there is some problem.

I am now buying a qlogic2200 to try if it is better.
Can someone tell me best drivers for qlogic2200?


Thanks again!


-- 
Mario Giammarco



  reply	other threads:[~2003-11-24 11:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21 19:37 Bad fibre channel performance: need howto Mario Giammarco
2003-11-21 20:05 ` Erling Nygaard
2003-11-24 10:55 ` Fabien Salvi
2003-11-24 11:30   ` Mario Giammarco [this message]
2003-11-24 15:26     ` Fabien Salvi

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=1069673445.1231.18.camel@cala \
    --to=mgiammarco@virgilio.it \
    --cc=fabien@cri74.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox