Was the xelerated architecture talking about a completely protocol independent chip design ? Nick is talking about In-
silicon implementation of forwarding abstractions that has a general applicability to any type of communications forwarding problem.
You left a key leader in software defined networks off of your list....BROCADE COMMUNICATIONS. Brocade is using a combination of ASICs, FPGAs and high-performance network processors in many of their current products and has paved the way for SDNs ahead of our competitors!
A company called Spider Systems used to make network hardware (routers, bridges, terminal servers and SNMP probes) based on the Intel 386 and 960 processors back in the 1990's. Cisco then moved to custom ASIC's and RFC protocols. I have a couple of Squiggle magazines from this time.
nick should take a look at xelerated dataflow architecture which was created in 2000 - that solves the packet processing excatly like he is suggesting with a very deep pipeline of classify action blocks and has fully programmable dataflow processor element which gives hundred percent deterministic behaviour
so the new breed of network processors that nick wrote a paper on has been around for 13 years
xelerated was bought by marvell for a few years ago and is still til this date the only programmable npu that is deterministic by design
I am sure that ASICs will be around for a long time (longer than we expect anyway), but the trend has been away from full custom ASICs towards FPGAs/programmables for some time now. The cost in time and money to develop full custom ASICs has been the impetus for many designs to switch to FPGAs. Given the improved performance/cost/size of the current FPGA families with on die processors I would only expect this trend to continue. With the development of software defined networking and the time for it to mature it makes a logical next step. I wonder how many companies will be left behind..?
That's not fully correct. The IXP1200 (and I believe its predecessors), featured an ARM processor for control plane processing along with 6 microengine processors specialized for packet processing.
Still... this is interesting that it's coming up again.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.