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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 28 Feb 2015 15:02:33 -0500 (EST)
From:	David Miller <>
Subject: Re: Flows! Offload them.

From: Tom Herbert <>
Date: Thu, 26 Feb 2015 10:15:24 -0800

> But, routing (aka switching) in the stack is not configured through
> TC. We have a whole forwarding and routing infrastructure (eg.
> iproute) with optimizations that  allow routes to be cached in
> sockets, etc. To me, it seems like offloading that basic functionality
> is a prerequisite before attempting to offload more advanced policy
> mechanisms of TC, netfilter, etc.


I think this is the most important post in this entire thread.

The current proposal here is jumping the gun by several weeks if
not months.

We have no idea what roadblocks or design barriers we will hit
with just plain L2 and L3 forwarding yet.

Therefore it is premature to move over to making major decisions
about flow offloading before we've made more progress with the
more fundamental (and in my opinion much more important) offload

Jiri, if you want to implement an example set of classifiers in
software that can completely replace openvswitch's datapath, that's
fine.  And it's a completely independant task to designing how we'll
offload flows to hardware in the future.
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists