Tuesday, October 4, 2011

Netronome discloses processor architecture requirements for 100 Gbps next gen firewall and OpenFlow designs

SANTA CLARA, USA: Netronome announced that Niel Viljoen, founder and chief development officer, will disclose new architecture requirements for processors being used in flow-based 100 Gbps communications designs, such as next-generation firewalls and OpenFlow switches and routers.

Viljoen’s presentation will take place at The Linley Group’s Tech Processor Conference, which focuses on networking and communications. The event is on October 5 and 6 at the Double Tree hotel in San Jose, California. Mr. Viljoen’s presentation and panel session both take place on Thursday October 6, during Session 7, “100Gbps Networking.”

“As the industry’s foremost event focused exclusively on processors, The Linley Tech Processor Conference provides a forum for industry leaders to share the latest developments in processor and related technologies,” said Joseph Byrne, an analyst with The Linley Group. “Netronome is a leader in flow processing solutions, and their insight on architectural requirements for processors targeting next-generation firewall and OpenFlow switching will be valuable information for our attendees.”

Viljoen will discuss the use of high-performance, programmable, highly-threaded, many-core processors in communications designs that require stateful processing of millions of simultaneous flow at 100Gbps and beyond. He will focus on processor architectural considerations to enable high-bandwidth and low-latency access to memory, a key bottleneck in scaling L4-L7 designs to 100Gbps. Mr. Viljoen will also participate in a Q&A panel with executives from Radisys and Xelerated.

“New processor architecture must overcome many new challenges when trying to handle millions of flows at 100Gbp packet rates, specifically a multi-threaded approach that hides memory latency,” said Viljoen. “Several challenges exist including on-chip memory optimization for increased access and reduced latency, recursive flow state lookups, and scalable access to packet data in local memory.”

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.