public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Chip Coldwell <coldwell@frank.harvard.edu>
Cc: Gerhard Schneider <gs@ilsb.tuwien.ac.at>, linux-scsi@vger.kernel.org
Subject: Re: SCSI tape access on 2.6 kernels?
Date: Tue, 24 Jan 2006 12:23:06 -0800	[thread overview]
Message-ID: <20060124202306.GA8422@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601241251460.23364@localhost.localdomain>

On Tue, Jan 24, 2006 at 12:52:36PM -0500, Chip Coldwell wrote:

> Put
> 
> options st try_direct_io=0

> 
> in /etc/modprobe.conf.  Direct I/O defeats read-ahead, and
> significantly (factor of >5) degrates read performance.  I don't know
> about writes.

For tape???

-- Patrick Mansfield

  reply	other threads:[~2006-01-24 20:23 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 [this message]
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
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=20060124202306.GA8422@us.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=coldwell@frank.harvard.edu \
    --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