Intel's Itanium on Launch Pad
After more than six years of effort, Intel is finally ready to deploy its first processor based on the IA-64 instruction set, which it co-developed with Hewlett-Packard. The chip, named Itanium, is designed to go where no Pentium has gone before: the high end of the server market. When it arrives, Itanium will open doors not just for Intel but also for Linux. Today, a few large companies ship the vast majority of big servers. Sun, HP, IBM and Compaq servers rely mainly on proprietary RISC processors and proprietary versions of UNIX. But with the turbo-charged Itanium, many other vendors will deliver servers that match the power of these proprietary machines. These vendors are likely to rely on Linux or one of two key competitors: Monterey UNIX or Windows 2000.
Intel is no stranger to the server market. Its chips have been used in PC servers for years, and in 1998, the company introduced the Xeon product line specifically for bigger systems. But there is little to distinguish the latest Xeon products from the Pentium III chips in PCs: they use the same CPU, have the same bus bandwidth and remain limited to 32-bit virtual addressing. Itanium is Intel's first CPU designed from the ground up for server applications. For starters, the chip offers 64-bit addressing, providing programmers with much more flexibility when dealing with large objects and data sets. RISC processors have included 64-bit addressing for nearly a decade.
Instead of simply extending the aging x86 instruction set to 64 bits, Intel decided to leap to a new instruction set, IA-64. This state-of-the-art design includes a host of performance-enhancing features—such as predication, speculation and register frames—that are not found in x86 or RISC processors.
The general intent of these features is to give the compiler more control over the hardware. In theory, the compiler can make better decisions about how to group and order instructions for optimal performance. Furthermore, the processor hardware is simplified by relying on the compiler to make these decisions. Simpler processors can be both faster and less expensive to manufacture. Many previous instruction sets have failed to gain significant market share. The problem has been incompatibility with existing software. Itanium solves this problem by including an x86 translation unit on the chip. This unit can process any existing x86 application, albeit at a lower speed than an application that has been recompiled for IA-64.
Intel has already produced hundreds of Itanium prototypes that are being used to validate new IA-64 hardware and software. Although there may be a few glitches remaining, the project appears on track. More than two dozen vendors plan to deploy Itanium systems, with the first systems appearing this fall.
In fact, nearly every major server vendor except Sun Microsystems has endorsed IA-64. Over time, HP will convert its entire line of RISC systems to the new architecture, as will SGI. IBM and Compaq will continue to develop RISC processors and systems, but will also deploy a broad range of IA-64 products. Companies such as Acer, Dell and Gateway will add Itanium to their Xeon server lines. With all of this backing, IA-64 is likely to grab at least 60% of the server market by 2003, according to a new report “Intel's Itanium and IA-64” from MicroDesign Resources. This would represent a big change from today's market, which is split among a variety of platforms. Linux holds 25% of the server market, according to IDC, a number that is rising rapidly. Although Linux is offered on several RISC platforms, the makers of these systems prefer to sell their own proprietary UNIX versions. Linux has been most popular on x86 systems from PC server makers. These vendors are most likely to benefit from Itanium. Current Intel processors can't match the performance and bandwidth of the best RISC systems, limiting PC server makers to low-end and mid-range systems. Using Itanium and Intel's new Lion motherboard, PC server makers will push into high-end markets, taking Linux with them.
Linux faces strong competitors in the Itanium market. IBM and SCO are merging their versions of UNIX, AIX and UnixWare into an IA-64 operating system known as Monterey. Based on the AIX kernel, Monterey offers reliability and scalability features from IBM's high-end servers. Because of the popularity of UnixWare, Monterey is a natural choice for Itanium systems from Compaq, Dell and, of course, IBM. Microsoft hopes to dominate the IA-64 market with a 64-bit version of its Windows 2000 operating system. Most PC server vendors will offer this as the default choice for Itanium systems. Previous Microsoft server products lack robustness and do not scale well beyond four processors; the company is working to fix these problems, but how long this will take remains to be seen. For small and mid-range servers, however, Windows will no doubt be a popular choice.
Linux's open-source model provides an advantage over these competitors, and it continues to gain features that will help it better compete against the likes of Monterey. As IA-64 processors displace proprietary RISCs from the high-end market, they create opportunities for newer operating systems. This platform change should boost Linux's prospects.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Managing Linux Using Puppet
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Doing for User Space What We Did for Kernel Space
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
- Rogue Wave Software's Zend Server
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide