Neterion develops virtualisation architecture


Neterion develops virtualisation architecture

Neterion, an industry leader in the 10 Gigabit Ethernet adapter market for server and storage environments, has launched Hyperframe, an I/O Virtualization (IOV) architecture that provides end-to-end virtualisation for the enterprise.

The company says that platforms that will benefit from this new technology span all elements of the datacentre and that benefits to end users of an IOV-based networking architecture include cost savings, flexibility performance, isolation and reliability

Features within the Hyperframe architecture include: multiple separate receive and transmit queues;  independent Direct Memory Access engines; separate network addresses; ability to classify and steer receive traffic; sophisticated interrupt schemes; separate register sets; separate copies of the configuration space; ability to direct packets through the PCI-Express fabric.

Neterion's current line of Xframe 10 Gigabit Ethernet adapters already include most of Hyperframe's features. Future generation Xframe products will offer support of Hyperframe, making efficient and robust IOV both affordable and available off-the-shelf.

"Today, server and storage virtualisation is delivering significant cost reduction and asset optimisation benefits to IT managers in corporate datacentres," comments Dave Zabrowski, president and CEO of Neterion.

"Hyperframe is designed to provide hardware support at the I/O component level. Neterion's line of products is offering exclusive features that allow optimisation of the network interface in a virtualised environment," he adds. 


Related Topics: Server hardware, VIEW ALL TOPICS

Email Alerts

Register now to receive IT-related news, guides and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

COMMENTS powered by Disqus  //  Commenting policy