From: Thomas Zimmerman <thomas@zimres.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Ess Solo-1 interrupt behaviour
Date: Tue, 19 Feb 2002 12:09:51 -0800 [thread overview]
Message-ID: <20020219200951.GA6615@darklands.zimres.net> (raw)
In-Reply-To: <E16d8GI-0000CS-00@the-village.bc.nu> <200202191412.g1JECvV12317@ibe.miee.ru>
In-Reply-To: <200202191412.g1JECvV12317@ibe.miee.ru>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On 19-Feb 05:12, Samium Gromoff wrote:
> " Alan Cox wrote:"
> >
> > > > Thats an esd bug. ESD tries to use ridiculously small fragment sizes
> > > >
> > > Wait, wait, but my ISA Vibra 16 generates 20+ times less interrupts, with the
> > > _same_ esd!
> >
> > Yes. It has diff fragment limits
> >
> So the point is we should fix esd, not the solo-1 driver, i presume?
> (esd_fixed -> irq_load_fixed -> disk_io_is_back)... sounds ok
>
> EOT
>
> regards, Samium Gromoff
It would be EOT, but there don't seem to _be_ any esd developers. I'd take a
look but my C skills max out at about "hello world", and there wouldn't be
anyone to make a new release (google couldn't find a esd homepage at least).
Maybe the gnome/ximian folks are taking bug reports/fixes in their packages.
Who knows? This has come up several times with nary a peep from a esd
developer.
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-02-19 20:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 12:52 Samium Gromoff
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 [this message]
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=20020219200951.GA6615@darklands.zimres.net \
--to=thomas@zimres.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 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®