public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Gerhard Schneider <gs@ilsb.tuwien.ac.at>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: linux-scsi@vger.kernel.org
Subject: Re: SCSI tape access on 2.6 kernels?
Date: Tue, 24 Jan 2006 22:01:04 +0100	[thread overview]
Message-ID: <43D69590.5050003@ilsb.tuwien.ac.at> (raw)
In-Reply-To: <Pine.LNX.4.63.0601242251190.6350@kai.makisara.local>

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

Kai Makisara schrieb:

> The only thing that could be seen in Gerhard's tests with try_direct_io=0 
> should be higher CPU load. It probably won't have any effect on the speed 
> in these tests.
> 
> Disabling direct i/o helps in fixed block mode if the application's read() 
> and write() byte counts are small, e.g., 10 kB. With 64 kB it should not 
> have any effect. Additionally, Gerhard is probably using variable block 
> mode and there is no read-ahead. There is write-behind which is disabled 
> when doing direct i/o but this should have no effect since if the HBA is 
> able to sustain the speed the drive requires.
> 

I fear you're right. There hasn't been any significant difference in
write/read speed when enabling/disabling direct i/o (significant doesn't
mean a speedup of 20-100% - I want to see more than 40MB/s on a LTO-3
tape drive, and not 1.2)..

Different fixed and variable block sizes didn't show significant speed
increases, too.. - and I still expect a kernel problem, not a tape
problem..

Tomorrow I will compile a kernel < 2.6.12 and redo testing..

                                             GS

-- 
Gerhard Schneider
Institute of Lightweight Design and         e-Mail: gs@ilsb.tuwien.ac.at
Structural Biomechanics (E317)                 Tel.:   +43 1 58801 31716
Vienna University of Technology / Austria      Fax:    +43 1 58801 31799
A-1040 Wien, Gusshausstrasse 27-29     http://www.ilsb.tuwien.ac.at/~gs/



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  parent reply	other threads:[~2006-01-24 21:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 10:42 SCSI tape access on 2.6 kernels? Gerhard Schneider
2006-01-24 12:56 ` Gerhard Schneider
2006-01-24 17:52 ` Chip Coldwell
2006-01-24 20:23   ` Patrick Mansfield
2006-01-24 20:36     ` Chip Coldwell
2006-01-25 21:10       ` Kai Makisara
2006-01-26 16:11         ` Chip Coldwell
2006-01-26 16:39           ` Chip Coldwell
2006-01-26 17:39             ` Dead Adaptec AHA-2940U2/U2W while ripping a CD Mathieu Chouquet-Stringer
2006-01-26 21:54           ` SCSI tape access on 2.6 kernels? Kai Makisara
2006-01-27 15:40             ` Chip Coldwell
2006-01-27 17:56               ` Kai Makisara
2006-01-24 20:56   ` Kai Makisara
2006-01-24 20:58     ` Chip Coldwell
2006-01-24 21:01     ` Gerhard Schneider [this message]
2006-01-25 16:08       ` Chip Coldwell
2006-01-25 16:25         ` Denny Page
2006-01-25 19:03           ` Gerhard Schneider
2006-01-24 19:43 ` Denny Page
2006-01-24 20:50 ` Kai Makisara
2006-01-24 21:12   ` Gerhard Schneider
2006-01-25 21:26   ` 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=43D69590.5050003@ilsb.tuwien.ac.at \
    --to=gs@ilsb.tuwien.ac.at \
    --cc=Kai.Makisara@kolumbus.fi \
    --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