From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Ross Biro <ross.biro@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.10-ac1
Date: Mon, 27 Dec 2004 16:54:50 +0100 [thread overview]
Message-ID: <58cb370e04122707544be6d600@mail.gmail.com> (raw)
In-Reply-To: <41D02EEC.4090000@domdv.de>
On Mon, 27 Dec 2004 16:49:00 +0100, Andreas Steinmetz <ast@domdv.de> wrote:
> Bartlomiej Zolnierkiewicz wrote:
> > Workaround it if it is possible. If this is really a unfixable hardware problem
> > (hard to believe - other OS-es would be also bitten by the issue) shouldn't it
> > be workaround differently anyway by something like "ide=serialize_all" (which
> > is much saner from IDE POV than "idex=serialize") ?
>
> Bad. This would neatly kill my raid 5 setup performance wise. Call this
> idea a big step sideways. Doing a ide2=serialize leaves all three disks
> running without serialization unless the dvd-rw is used. Just to make it
> clear:
> ide0 -> onboard, 1 master (disk)
> ide1 -> onboard, 1 master (disk)
> ide2/3 -> pci, 2 master (disk,dvd-rw)
> Your idea would serialize all ide accesses which would slow down all
> disks not affected by the problem requiring serialization.
Ah, so the problem only affects native PCI IRQs.
Is it possible that it is a buggy IDE host driver not a generic IDE problem?
next prev parent reply other threads:[~2004-12-27 16:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 23:31 Linux 2.6.10-ac1 Alan Cox
2004-12-27 0:57 ` Bartlomiej Zolnierkiewicz
2004-12-27 1:25 ` Andreas Steinmetz
2004-12-27 1:40 ` Bartlomiej Zolnierkiewicz
2004-12-27 14:28 ` Alan Cox
2004-12-27 15:46 ` Bartlomiej Zolnierkiewicz
2004-12-27 14:45 ` Ross Biro
2004-12-27 15:38 ` Bartlomiej Zolnierkiewicz
2004-12-27 15:49 ` Andreas Steinmetz
2004-12-27 15:54 ` Bartlomiej Zolnierkiewicz [this message]
2004-12-27 16:02 ` Andreas Steinmetz
2004-12-27 16:54 ` Alan Cox
2004-12-27 14:36 ` Rafael J. Wysocki
2004-12-27 14:57 ` Andreas Steinmetz
2004-12-27 14:33 ` Alan Cox
2004-12-27 20:31 ` Rogério Brito
2004-12-27 20:43 ` Michal Schmidt
2004-12-28 0:45 ` Alan Cox
2004-12-28 2:44 ` Rogério Brito
2004-12-30 4:41 ` Gene Heskett
2004-12-30 5:05 ` Gene Heskett
2004-12-30 23:38 ` Alan Cox
2004-12-31 1:06 ` Gene Heskett
2004-12-31 9:57 ` Jan Dittmer
2004-12-31 12:05 ` Gene Heskett
2004-12-31 12:38 ` Jan Dittmer
2004-12-31 13:18 ` Gene Heskett
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=58cb370e04122707544be6d600@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.biro@gmail.com \
/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.