netdev - Re: Flows! Offload them.

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20150228213132.GA21610@nanopsycho.orion>
Date:	Sat, 28 Feb 2015 22:31:32 +0100
From:	Jiri Pirko <jiri@...nulli.us>
To:	David Miller <davem@...emloft.net>
Cc:	therbert@...gle.com, simon.horman@...ronome.com,
	netdev@...r.kernel.org, nhorman@...driver.com, andy@...yhouse.net,
	tgraf@...g.ch, dborkman@...hat.com, ogerlitz@...lanox.com,
	jesse@...ira.com, jpettit@...ira.com, joestringer@...ira.com,
	john.r.fastabend@...el.com, jhs@...atatu.com, sfeldma@...il.com,
	f.fainelli@...il.com, roopa@...ulusnetworks.com,
	linville@...driver.com, shrijeet@...il.com,
	gospo@...ulusnetworks.com, bcrl@...ck.org
Subject: Re: Flows! Offload them.

Sat, Feb 28, 2015 at 09:02:33PM CET, davem@...emloft.net wrote:
>From: Tom Herbert <therbert@...gle.com>
>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.
>
>+1
>
>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
>facilities.

Fair enough. I just felt that the flows are happening just now
(John's work) so I wanted people to stay in focus. But I completely
agree that plain L2, L3 forwarding should be handled first. Then some
of the quirks connected with that, flows and other stuff after.

>
>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.

Nod. Will do that.
--
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