Merged (and to be merged) for 2.6.22
- Lots of networking changes, including improvements to the forward
receive timeout recovery (RFC4138)
implementation, a YeAH-TCP
congestion control [PDF] implementation, a TCP
Illinois congestion control implementation, and a new RxRPC secure
socket layer (along with support for using RxRPC in the AFS
filesystem).
Also, the old, IPv4-only connection tracking code has been removed as
per the feature removal schedule.
- The cfg80211 patches - a new, netlink-based interface for configuring
wireless interfaces - have been merged. At the same time, the netlink
version of the "wireless extensions" interface has been removed.
- The OCFS2 filesystem now has sparse file support.
- The UBI
patch, which performs flash-aware partitioning and volume management,
has been merged.
- New drivers for USB webcams based on zr364xx chipsets, AT26Fxxx
dataflash devices, CM-X270-based NAND flash memory, Freescale SOC USB
controllers, and Marvell Libertas 802.11 adaptors (used in the OLPC
system).
It's also worth noting that the IVTV video driver, long out of the mainline, has finally been merged. "
It took three core maintainers, over four years of work, eight new i2c modules, eleven new V4L2 ioctls, three new DVB video ioctls, a Sliced VBI API, a new MPEG encoder API, an enhanced DVB video MPEG decoding API, major YUV/OSD contributions from Ian and John, web/wiki/svn/trac support from Axel Thimm, (hardware) support from Hauppauge, support and assistance from the v4l-dvb people and the many, many users of ivtv to finally make it possible to merge this driver into the kernel.
" - A new "sony-laptop" layer which replaces sonypi and provides better
Sony support. The old "ibm_acpi" module has been renamed
"thinkpad-acpi," and it features improved support for those laptops.
- The CFQ I/O scheduler has been reworked. Taking inspiration from the CFS CPU scheduler, it now uses a red-black tree to sort pending requests by expected execution time and track them.
Changes visible to kernel developers include:
- The eth_type_trans() function now sets the
skb->dev field, consistent with how similar functions for
other link types operate. As a result, many Ethernet drivers have
been changed to remove the (now) redundant assignment.
- The header fields in the sk_buff structure have been renamed
and are no longer unions. Networking code and drivers can now just
use skb->transport_header,
skb->network_header, and skb->skb_mac_header.
There are new functions for finding specific headers within packets:
tcp_hdr(), udp_hdr(), ipip_hdr(), and
ipipv6_hdr().
- Also in the networking area: the packet scheduler has been reworked to use ktime values rather than jiffies.
Those who are curious about what else might get in to 2.6.22 can have a look at Andrew Morton's 2.6.22 merge plans document. Interestingly, Lguest, the signalfd work, and the SLUB allocator are all planned for merging, but all have become less certain since:
- There have been some complaints that Lguest has not been sufficiently
reviewed. Since this development is independent and will not bother
those who do not use it, the concerns are less likely to delay its
inclusion.
- Signalfd has a new competitor in the form of the pollfs patch. Pollfs takes
takes a different approach to many of the same problems and throws in
polling for futex operations as well. It is far from clear that
pollfs is better (some of the early reviews have been on the
unfavorable side), but the process of figuring out whether that is
true could delay signalfd past the closing of the merge window.
- The SLUB allocator has also been subject to concerns that it has not been sufficiently tested for such a fundamental change. Additionally, there seems to be a difference of goals between Andrew Morton (who would like to see SLUB eventually replace the current slab allocator) and SLUB developer Christoph Lameter, who had seen the two coexisting indefinitely. Chances are these issues will get worked out and SLUB will go in as scheduled.
There are a few things of interest which are not on Andrew's list. The reiser4 filesystem seems certain to sit out (at least) another cycle, despite a resurgence in interest in getting it ready for inclusion. Xen is not mentioned, but it seems that, behind the scenes, it is being worked on. So Xen could actually show up before the merge window closes. There will be no major scheduler rework in 2.6.22; it's too soon for any of those patches to go in. The anti-fragmentation patches look likely to wait a little longer; Andrew worries that they still haven't seen enough review and benchmarking despite many iterations over a few years. The integrity management patches are considered to be unready and will not be merged.
Beyond that, there will be doubtless be surprises over the next week or so;
stay tuned.
Index entries for this article | |
---|---|
Kernel | Releases/2.6.22 |
Posted May 3, 2007 9:30 UTC (Thu)
by johill (subscriber, #25196)
[Link]
Posted May 3, 2007 11:25 UTC (Thu)
by pointwood (guest, #2814)
[Link] (2 responses)
Is there more info about this somewhere?
Posted May 3, 2007 12:30 UTC (Thu)
by nowster (subscriber, #67)
[Link] (1 responses)
Posted May 3, 2007 17:14 UTC (Thu)
by hmh (subscriber, #3838)
[Link]
I heavily suggest a visit to ThinkWiki and the archive for the linux-thinkpad mailinglist, the two major sources of information on ThinkPad Linux support. Anyway, there is nothing breath-taking in thinkpad-acpi for 2.6.22, the mass of new features merge happened in 2.6.21. 2.6.22 thinkpad-acpi will feature a hwmon-compatible interface for the temperatures and fan control, though. There is also a rename of the backlight device to "thinkpad_screen" and some other assorted minor stuff.
Posted May 3, 2007 14:21 UTC (Thu)
by mattdm (subscriber, #18)
[Link]
Posted May 3, 2007 20:19 UTC (Thu)
by jengelh (guest, #33263)
[Link] (3 responses)
Posted May 6, 2007 21:41 UTC (Sun)
by zdzichu (subscriber, #17118)
[Link] (1 responses)
Posted May 6, 2007 22:06 UTC (Sun)
by jengelh (guest, #33263)
[Link]
But first, here is the `man 7 netlink` excerpt, which is why I asked what's with netlink:
>Netlink is not a reliable protocol. It tries its best to deliver a message to its destination(s), but may drop messages when an out-of-memory condition or other error occurs. (For reliable transfer the sender can request an acknowledgement from the receiver by setting the NLM_F_ACK flag.)
And handling the extra ACK increases code complexity (it may get hidden in wrapper libraries like libnetlink though).
Posted May 13, 2007 15:18 UTC (Sun)
by muwlgr (guest, #35359)
[Link]
Posted May 4, 2007 18:13 UTC (Fri)
by i3839 (guest, #31386)
[Link]
It seems clear that everyone wants SLUB, the disagreement is about how fast it should replace SLAB. So the question isn't whether SLUB will be merged in the next release, but when it will enabled by default.
Christoph Lameter timeline can be found at:
http://lkml.org/lkml/2007/5/2/434
It's interesting to note that he thinks that SLUB can replace SLOB as well.
Actually, the note about cfg80211 isn't quite true; we have so far only merged the kernel components and a very slim sysfs userspace interface, the netlink part is not going into mainline yet.cfg80211
"# The old "ibm_acpi" module has been renamed "thinkpad-acpi," and it features improved support for those laptops."Thinkpad-acpi?
You might want to read the archive of the ibm-acpi mailing list:
http://news.gmane.org/gmane.linux.acpi.ibm-acpi.devel
Thinkpad-acpi?
Thinkpad-acpi?
Clarification -- from the documentation, it doesn't look like sony-laptop in its current state is a complete replacement for sony-pi. For example, it doesn't cover the special keys and jogdial which are reported in this way.sonypi
I don't get the hype about netlink. It's unrealiable compared to ioctls...Merged (and to be merged) for 2.6.22
Nice troll.Merged (and to be merged) for 2.6.22
Nice post. Instead of just calling me a troll you could have posted a pointer as to why netlink is preferred.Merged (and to be merged) for 2.6.22
In about 10 years, Linux may easily come to communicating everything via 9P :>Merged (and to be merged) for 2.6.22
The text about SLUB isn't quite correct:Merged (and to be merged) for 2.6.22