Hi Gopi I have started two attempts to do basically this and have the following (not very well thought out) comments:
+ you probably need a new ofproto. this is a lot harder than creating a new dpif. read PORTING.md. + a lot of code that you need in your new ofproto actually happens at the dpif layer. so much so that I decided to make my new ofproto also use dpif for at least those functions that it can usefully use. + ideally, we might consider a new ofproto (called for example ofproto-ttp) which acts as a general ofproto for lower layers base on particular TTPs. code that directly parsed a TTP would be handy, either to operate directly on the TTP or generate code. + then we could slot in entities called for example ttps, including a Broadcom ttp, which would itself interact with something like the OF-DPA code. + you would be slightly crazy to try to create this in your own fork, judging by how much OVS and the OpenFlow specs are changing - better to get agreement from the OVS community to support this. + check out project Atrium (good luck finding the code - you may need to be a member of the ONF). it's not based on OVS but on something older (and possibly simpler and less up to date) called Indigo. I would be interested in carrying out further discussions on this, but you probably want to get someone like Ben Pfaff interested... I am currently considering how best to implement OF-DPA, so it's possible that I can offer of team of 5 or more engineers to do some of the heavy lifting on this... Cheers Tony Hi, I would like to know if anyone tried integrating OF-DPA software with the OVS code ? I didn't find much information on this topic.And is there any open source software similar to OF-DPA? Regards,Gopi _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
