public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Denny Page <denny@cococafe.com>
To: Chip Coldwell <coldwell@redhat.com>
Cc: Gerhard Schneider <gs@ilsb.tuwien.ac.at>,
	Kai Makisara <Kai.Makisara@kolumbus.fi>,
	linux-scsi@vger.kernel.org
Subject: Re: SCSI tape access on 2.6 kernels?
Date: Wed, 25 Jan 2006 08:25:53 -0800	[thread overview]
Message-ID: <43D7A691.1040606@cococafe.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601251107480.5181@localhost.localdomain>

I agree.  In my case, the problem is also initial negation: 3 MB/s :-(.

Denny


Chip Coldwell wrote:
> I'm curious -- what was the impact on performance of disabling direct
> I/O in your case?
>
> I agree with Kai that the biggest performance hit is the 20 MB/s
> negotiated bus speed.
>
> Chip
>

  reply	other threads:[~2006-01-25 16:26 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
2006-01-25 16:08       ` Chip Coldwell
2006-01-25 16:25         ` Denny Page [this message]
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=43D7A691.1040606@cococafe.com \
    --to=denny@cococafe.com \
    --cc=Kai.Makisara@kolumbus.fi \
    --cc=coldwell@redhat.com \
    --cc=gs@ilsb.tuwien.ac.at \
    --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