From: David Daney <ddaney@caviumnetworks.com>
To: Netdev <netdev@vger.kernel.org>
Subject: Custom hardware Qdisc...
Date: Fri, 11 Dec 2009 10:26:08 -0800 [thread overview]
Message-ID: <4B228EC0.80105@caviumnetworks.com> (raw)
Our hardware (Octeon SOC) has fairly flexible packet output queuing that
can be done completely in hardware.
I am thinking of trying to take advantage of this in the driver
(currently in drivers/staging/octeon).
At a very hige level my tentative plan is to implement a custom Qdisc
that has an enqueue method that places the packets directly in the
output queues after they are classified.
The dequeue method would be a noop returning NULL because once the
packets are on the queues, no further action is needed from the driver.
Does doing something like this seem plausible? If not, what are the
main problems I might be overlooking?
Thanks in advance,
David Daney
next reply other threads:[~2009-12-11 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 18:26 David Daney [this message]
2009-12-11 22:40 ` Custom hardware Qdisc David Miller
2009-12-12 0:58 ` David Daney
2009-12-12 1:05 ` David Miller
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=4B228EC0.80105@caviumnetworks.com \
--to=ddaney@caviumnetworks.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).