netdev - Custom hardware Qdisc...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4B228EC0.80105@caviumnetworks.com>
Date:	Fri, 11 Dec 2009 10:26:08 -0800
From:	David Daney <ddaney@...iumnetworks.com>
To:	Netdev <netdev@...r.kernel.org>
Subject: Custom hardware Qdisc...

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html