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
| ||
|
Message-ID: <20140826152217.GA1843@nanopsycho.lan> Date: Tue, 26 Aug 2014 17:22:17 +0200 From: Jiri Pirko <jiri@...nulli.us> To: Jamal Hadi Salim <jhs@...atatu.com> Cc: Roopa Prabhu <roopa@...ulusnetworks.com>, Thomas Graf <tgraf@...g.ch>, John Fastabend <john.fastabend@...il.com>, Scott Feldman <sfeldma@...ulusnetworks.com>, netdev <netdev@...r.kernel.org>, David Miller <davem@...emloft.net>, Neil Horman <nhorman@...driver.com>, Andy Gospodarek <andy@...yhouse.net>, dborkman <dborkman@...hat.com>, ogerlitz <ogerlitz@...lanox.com>, jesse@...ira.com, pshelar@...ira.com, azhou@...ira.com, ben@...adent.org.uk, stephen@...workplumber.org, jeffrey.t.kirsher@...el.com, vyasevic@...hat.com, xiyou.wangcong@...il.com, john.r.fastabend@...el.com, edumazet@...gle.com, f.fainelli@...il.com, linville@...driver.com, dev@...nvswitch.org, jasowang@...hat.com, ebiederm@...ssion.com, nicolas.dichtel@...nd.com, ryazanov.s.a@...il.com, buytenh@...tstofly.org, aviadr@...lanox.com, nbd@...nwrt.org, alexei.starovoitov@...il.com, Neil.Jerram@...aswitch.com, ronye@...lanox.com, Shrijeet Mukherjee <shm@...ulusnetworks.com> Subject: Re: [patch net-next RFC 10/12] openvswitch: add support for datapath hardware offload Tue, Aug 26, 2014 at 04:58:54PM CEST, jhs@...atatu.com wrote: >On 08/26/14 10:06, Jiri Pirko wrote: > >>Yes. Flows are phase one. The api will be extended in for whatever is >>needed for l2/l3 as you said. Also I see a possibility to implement the >>l2/l3 use case with flows as well. > >And as a note: This is where i have the disagreement. >It is good there is acknowledgement you are handling flows for now. >Or whatever tuples you defined as "flow". I dont think L2 or 3 fit >in that. If thats not what you are saying then we are in agreement. I do not think that really matters. Phase one is flows. After that we can focus on l2/l3. If we would be able to fit in in flows (some drivers may), then ok. If not, we extend the api with couple of more l2/l3 related ndos. I see no problem there. -- 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
Powered by blists - more mailing lists