From: Charles Eidsness <charles.eidsness@ieee.org>
To: ppopov@embeddedalley.com
Cc: linux-mips@linux-mips.org
Subject: Re: Au1000 Ethernet Driver using NAPI
Date: Wed, 08 Dec 2004 20:05:19 -0500 [thread overview]
Message-ID: <41B7A4CF.7090203@ieee.org> (raw)
Pete Popov wrote:
>
>Very cool, thanks. Is the patch for 2.4 or 2.6?
>
>Pete
Hi Pete,
It's for 2.6, I'm not sure if it will work on 2.4.
There are a couple of possible issues with this method that I probably
should have mentioned in my first email. Since the Au1000 shares an
interrupt for the TX and RX streams I had to lump the two together and
as a result there may be an increase in TX latency. Also, the MAC's DMA
can only queue up a maximum of 4 packets at a time so depending on how
long the processor spends clearing out the queue there may be some
buffer overruns. I've experienced neither of these issues but my testing
so far has been pretty application specific.
Cheers,
Charles
Charles Eidsness wrote:
> Hi All,
>
> I was having a problem running a streaming audio application on my
> Au1000 processor when the Ethernet port was being bombarded with
> packets. All of the interrupt servicing was hogging my precious
> processing power and there was nothing left for my app. There's a new
> method for writing Ethernet drivers called NAPI which resolves this
> issue (somewhat). I converted the au1000's Ethernet driver to use
this
> method. If you're interested you can find a patch that applys my
changes
> to the most recent kernel here:
>
>
http://members.rogers.com/charles.eidsness/linux-au1000_eth.napi.patch
>
> Cheers,
> Charles
>
>
next reply other threads:[~2004-12-09 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 1:05 Charles Eidsness [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 20:31 Au1000 Ethernet Driver using NAPI Charles Eidsness
2004-12-08 23:34 ` Pete Popov
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=41B7A4CF.7090203@ieee.org \
--to=charles.eidsness@ieee.org \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@embeddedalley.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.