By Yehiel Engel, Commex Technologies
When moving from a single processor single core to a multi-processor multi-core system, are you finding that I/O performance does not scale at 10Gb/s? This article tells you why, and how you can solve the problem with content aware routing.
Currently all traffic arriving from I/O ports (e.g. network port or storage port) to server/appliance, passes through the platform hub (chipset) and is sent to the server processor(s)/core(s). The processor that receives the data is responsible for classifying and directing data frames to their final destination. This destination can be another I/O agent, either a network port or local/remote storage (i.e., disk).
In most cases the server processor only needs to inspect and process a small portion of the data frame (header or header fields), or even make automatic decisions (i.e., send compressed packets to decompress engine).
