From: net expert <netexpert201@gmail.com>
To: netfilter-devel@vger.kernel.org
Subject: netfilter Integration with hardware
Date: Thu, 21 Jan 2010 13:11:11 -0600 [thread overview]
Message-ID: <e8b4413d1001211111l1a08a109w8403572a0e9e68d3@mail.gmail.com> (raw)
Hello,
We have general purpose CPU (PPC) and an ASIC on our board. ASIC can
perform all lookups according to the packet address/port
source/destination,protocol type, MAC address source/destination.
Depending on the outcome of
the lookup ASIC can
- drop the packet
- forward the packet to one of the interfaces
- forward the packet to the CPU and so on.
We are running 2.6 Linux kernel in the CPU. Naturally I would like to
use netfilter for management of the hardware (ASIC) tables and use the
hardware to forward as many packets as possible without CPU
intervention.
I read through the documentation and started to study the source code.
It appears, that it's possible to solve the
problem. But I would like to avoid solving the same time problem
twice. Is there any example(s) for this type of integration ? any
documentation/tips/links could save me lot of time.
Thanks,
reply other threads:[~2010-01-21 19:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e8b4413d1001211111l1a08a109w8403572a0e9e68d3@mail.gmail.com \
--to=netexpert201@gmail.com \
--cc=netfilter-devel@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).