From: Samium Gromoff <root@ibe.miee.ru>
To: linux-kernel@vger.kernel.org
Subject: Ess Solo-1 interrupt behaviour
Date: Tue, 19 Feb 2002 15:52:24 +0300 (MSK) [thread overview]
Message-ID: <200202191252.g1JCqOR11998@ibe.miee.ru> (raw)
I`ve recently spotted that a solo1 pci soundcard generates
16000+ interrupts/second with esd started idling.
What strikes me as odd is that my old good isa sb16 vibra
does only 600+ interrupts.
Also i`ve had some strange experience of this interrupt load
affecting the disk io.
The situation was the next: i`ve had a large transfer to a samba
boxen with this poor solo1 soundcard. I would like to emphasize that i
turn off the drive write-caching ability in order to gain reliability,
and that with write cacheing the following issues are hardly noticeable.
So yes, i was copying large amount of data thru the 10mbit rtl8029s
to the samba box. What i`ve tested are two situations: with esd on ==
effective 16,5k interrupts/second, and with esd off, and thus no interrupts
generated by the solo1 card.
What i`ve noticed quite disappointed me: with esd turned on, the disk
writeout activity (well, the seek activity) was _much_ higher.
Ie i`ve stopped esd, the seekage dropped down, i`ve started esd -
seekage goes back.
So we basically have here two strange issues:
1. Ess Solo-1 driver generates awful lots of interrupts (16k/s)
2. Heavy interrupt load forces the elevator to make bad
decisions
Info: linux-2.4.17-rmap12e, p2-300 128M RAM, rtl8029 NIC, Ess Solo-1 SB
regards, Samium Gromoff
next reply other threads:[~2002-02-19 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 12:52 Samium Gromoff [this message]
2002-02-19 11:01 ` Alan Cox
2002-02-19 13:44 ` Samium Gromoff
2002-02-19 10:54 ` Zwane Mwaikambo
2002-02-19 11:13 ` William Lee Irwin III
2002-02-19 11:16 ` Alan Cox
2002-02-19 14:12 ` Samium Gromoff
2002-02-19 20:09 ` Thomas Zimmerman
2002-02-22 18:22 ` Thomas Sailer
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=200202191252.g1JCqOR11998@ibe.miee.ru \
--to=root@ibe.miee.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®