From: Felix Radensky <felix@embedded-sol.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Advice on network driver design
Date: Sat, 19 Feb 2011 15:37:43 +0200 [thread overview]
Message-ID: <4D5FC7A7.5050704@embedded-sol.com> (raw)
Hi,
I'm in the process of designing a network driver for a custom
hardware and would like to get some advice from linux network
gurus.
The host platform is Freescale P2020. The custom hardware is
FPGA with several TX FIFOs, single RX FIFO and a set of registers.
FPGA is connected to CPU via PCI-E. Host CPU DMA controller is used
to get packets to/from FIFOs. Each FIFO has its set of events,
generating interrupts, which can be enabled and disabled. Status
register reflects the current state of events, the bit in status
register is cleared by FPGA when event is handled. Reads or writes to
status register have no impact on its contents.
The device driver should support 80Mbit/sec of traffic in each direction.
So far I have TX side working. I'm using Linux dmaengine APIs to
transfer packets to FIFOs. The DMA completion interrupt is handled
by per-fifo work queue.
My question is about RX. Would such design benefit from NAPI ?
If my understanding of NAPI is correct, it runs in softirq context,
so I cannot do any DMA work in dev->poll(). If I were to use NAPI,
I should probably disable RX interrupts, do all DMA work in some
work queue, keep RX packets in a list and only then call dev->poll().
Is that correct ?
Any other advice and how to write an efficient driver for this
hardware is most welcome. I can influence FPGA design to some degree,
so if you think FPGA should be changed to improve things, please let
me know.
Thanks a lot in advance.
Felix.
next reply other threads:[~2011-02-19 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-19 13:37 Felix Radensky [this message]
2011-02-20 18:14 ` Advice on network driver design Micha Nelissen
2011-02-20 21:01 ` Felix Radensky
2011-02-20 19:13 ` arnd
2011-02-21 16:25 ` Felix Radensky
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=4D5FC7A7.5050704@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).