From: David Daney <ddaney@caviumnetworks.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Custom hardware Qdisc...
Date: Fri, 11 Dec 2009 16:58:50 -0800 [thread overview]
Message-ID: <4B22EACA.2060407@caviumnetworks.com> (raw)
In-Reply-To: <20091211.144021.192655356.davem@davemloft.net>
David Miller wrote:
> From: David Daney <ddaney@caviumnetworks.com>
> Date: Fri, 11 Dec 2009 10:26:08 -0800
>
>> Our hardware (Octeon SOC) has fairly flexible packet output queuing
>> that can be done completely in hardware.
>
> You haven't described sufficiently what your hardware is
> capable of.
>
Up to 16 output queues per port. With (almost) any combination of
absolute and weighted priorities between the various queues.
> Generally, implementing qdiscs specifically to support
> hardware features is not how things are handled.
>
I think I could emulate the default pfifo Qdisk fairly well in hardware.
By making it a Qdisc, the user would still be able to switch to one of
the software implementations if desired at runtime.
> But really we need to know a lot more about the details of your
> hardware to make any kind of real suggestions.
>
Well see above for the overview. I just wanted to get an idea if such
an approach would be highly frowned upon before coding anything up.
We see significant cacheline bouncing in the Qdisc code and can increase
packet forwarding rates by 10%-15% by setting the txqueuelen to zero
to disable the queuing. I would like to see if the same thing can be
achieved without throwing away the features of the Qdisc.
David Daney
next prev parent reply other threads:[~2009-12-12 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 18:26 Custom hardware Qdisc David Daney
2009-12-11 22:40 ` David Miller
2009-12-12 0:58 ` David Daney [this message]
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=4B22EACA.2060407@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=davem@davemloft.net \
--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).