From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6 ide i/o performance
Date: Mon, 04 Aug 2003 11:04:42 +0200 [thread overview]
Message-ID: <yw1xel01kd3p.fsf@users.sourceforge.net> (raw)
In-Reply-To: 200308021205.59280.vt@vt.fermentas.lt
Vitalis Tiknius <vt@vt.fermentas.lt> writes:
> i simultaneously burned (audio mode, without scsi emulation) and ripped cd's
> under 2.6.0-test2-mm2. devices are:
>
> ../ide/host0/bus1/target0/lun0/cd (Teac CD-W552E)
> ../ide/host0/bus1/target1/lun0/cd (Teac DV-516E).
>
> mobo is Intel 875. software is k3b-0.9, cdrtools-2.01_alpha18, grip-3.1.1, and
> cdparanoia-3.9.8 with all paranoia options on.
>
> when burning and ripping are performed separately, their speeds are approx.
> 42x and 6.3x. when simultaneously, 12x and 1.6x with no options touched.
>
> although devices are on the same controller (my first controller is
> SATA) and on the same bus, i'd rather expect linear and not almost
> square-law throughput regression observed. are the things expected
> to go this way, or there is some room for optimizations, etc.?
The first thing to do is to use separate cables for those devices, and
see if it helps.
--
Måns Rullgård
mru@users.sf.net
prev parent reply other threads:[~2003-08-04 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-02 10:05 2.6 ide i/o performance Vitalis Tiknius
2003-08-04 9:04 ` Måns Rullgård [this message]
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=yw1xel01kd3p.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.