News

Xeon to power Linux project for US defence department

Adopting 64-bit computing, Linux Networx will be one of the first companies to use Intel's Xeon processors with Intel Extended Memory 64 Technology (Intel EM64T).

Intel introduced its Xeon processor in June. The chip is the first Intel Xeon processor to offer Intel Extended Memory 64 Technology (Intel EM64T).

Linux will use the technology in the cluster-building work the company is doing for the Army Research Laboratory Major Shared Resource Centre (ARL MSRC). Linux Networx was selected by the US Department of Defense's High Performance Computing Modernization Program to build a 2,132-processor Evolocity IIA(E2) cluster for the ARL MSRC.

"We are excited Linux Networx will be one of the first computer suppliers to deliver a solution with our latest Intel Xeon processor, which includes support for DDR2 memory, increased memory addressability and new IO capabilities," said Phil Brace, director of marketing for Intel Enterprise Platforms Group.

"The use of Intel Xeon processors with Intel EM64T and a host of other new technologies in Linux Networx systems proves the technology capabilities in demanding production computing environments."

The project was initiated as a result of the Technology Insertion 2004 (TI-04) programme, an initiative to modernise the Department of Defense high performance computing capabilities.

The new Xeon chip is able to offer both 32 and 64-bit compatibility. Enhanced Intel SpeedStep Technology lets the processor dynamically adjust power up to 31%, which reduces overall cost and also minimises heat problems when processors run too long at one speed.

Written by LinuxWorld staff


Email Alerts

Register now to receive ComputerWeekly.com 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