Language Selection

English French German Italian Portuguese Spanish

Kernel Log: Coming in 3.2 (Part 3) - Architecture

Filed under
Linux

In keeping with the usual weekly release rhythm, Linus Torvalds issued the fourth release candidate of Linux 3.2 last Friday. It contains fewer changes than the two previous RCs, and Torvalds said that "things really are calming down pretty nicely", adding that it is even "suspiciously quiet." With the development of Linux 3.2 in progress, the Kernel Log is continuing its "Coming in 3.2" mini series. After describing the advancements in the kernel's network driver and infrastructure areas and those relating to filesystems, we will now cover the changes relating to the kernel's architecture and processor support; in the coming weeks, further articles will discuss the kernel's infrastructure and drivers.

Optimised encryption and decryption

An additional SHA1 implementation for x86-64 CPUs is designed to allow the hash algorithm to achieve higher throughputs by using SSE3 or AVX commands; according to the developer's measurement results, the implementation increased an IPSec connection's throughput on a Core 2 Quad from 344 to 464 Mbits/s.

rest here




More in Tux Machines

Leftovers: Gaming

Leftovers: Software

today's howtos

ACPI, kernels and contracts with firmware

This ends up being a pain in the neck in the x86 world, but it could be much worse. Way back in 2008 I wrote something about why the Linux kernel reports itself to firmware as "Windows" but refuses to identify itself as Linux. The short version is that "Linux" doesn't actually identify the behaviour of the kernel in a meaningful way. "Linux" doesn't tell you whether the kernel can deal with buffers being passed when the spec says it should be a package. "Linux" doesn't tell you whether the OS knows how to deal with an HPET. "Linux" doesn't tell you whether the OS can reinitialise graphics hardware. Read more