netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5

from [Tim Hockin] [Permanent Link][Original]
To: hadi@xxxxxxxxxx (jamal)
Subject: Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5
From: Tim Hockin <thockin@xxxxxxxxxx>
Date: Thu, 4 Oct 2001 08:03:27 -0700 (PDT)
Cc: sim@xxxxxxxxxxxxx (Simon Kirby), greearb@xxxxxxxxxxxxxxx (Ben Greear), mingo@xxxxxxx (Ingo Molnar), linux-kernel@xxxxxxxxxxxxxxx, kuznet@xxxxxxxxxxxxx (Alexey Kuznetsov), Robert.Olsson@xxxxxxxxxxx (Robert Olsson), bcrl@xxxxxxxxxx (Benjamin LaHaise), netdev@xxxxxxxxxxx, alan@xxxxxxxxxxxxxxxxxxx (Alan Cox)
In-reply-to: <Pine.GSO.4.30.0110040751040.9341-100000@shell.cyberus.ca> from "jamal" at Oct 04, 2001 07:54:19 AM
Sender: owner-netdev@xxxxxxxxxxx 
> Has nothing to do with specific hardware although i see your point.
> send me an eepro and i'll at least add hardware flow control for you.
> The API is simple, its up to the driver maintainers to use. This
> discussion is good to make people aware of those drivers.


is there a place where this is explained?  I'd be happy to make drivers on
which I work support this.  It's like ethtool - easy to do, but no one has
done it because they didn't know.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: Should IP addresses on interfaces not UP respond to ping?, Pekka Savola
Next by Date:  Re: Should IP addresses on interfaces not UP respond to ping?, Matthew G. Marsh
Previous by Thread:  Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5, jamal
Next by Thread:  Re: [announce] [patch] limiting IRQ load, irq-rewrite-2.4.11-B5, Ingo Molnar
Indexes:  [Date] [Thread] [Top] [All Lists]