Slashdot Mirror


Linux 3.3 Released

diegocg writes "Linux 3.3 has been released. The changes include the merge of kernel code from the Android project. There is also support for a new architecture (TI C6X), much improved balancing and the ability to restripe between different RAID profiles in Btrfs, and several network improvements: a virtual switch implementation (Open vSwitch) designed for virtualization scenarios, a faster and more scalable alternative to the 'bonding' driver, a configurable limit to the transmission queue of the network devices to fight bufferbloat, a network priority control group and per-cgroup TCP buffer limits. There are also many small features and new drivers and fixes. Here's the full changelog."

39 of 314 comments (clear)

  1. Keep it up. by Severus+Snape · · Score: 5, Insightful

    The Linux kernel guys show that constant steady frequent releases are the way forwards, note to GNOME and KDE guys, you got it wrong.

    1. Re:Keep it up. by houstonbofh · · Score: 5, Insightful

      That and the kernel guys actually put in features people want and need, not shove unwanted changes down the users thoughts...

    2. Re:Keep it up. by MrEricSir · · Score: 5, Funny

      shove unwanted changes down the users thoughts...

      You can uninstall GBrain and/or MindKontrol to prevent Gnome and KDE from controlling your thoughts.

      --
      There's no -1 for "I don't get it."
    3. Re:Keep it up. by Smauler · · Score: 4, Funny

      The Linux kernel guys show that constant steady

      I agree... 1 sec.

      frequent releases are the way forwards, note

      Argh... just got to...

      to GNOME and KDE

      update firefox...

      guys, you

      Again?

      got

      Must

      it

      finish

      wrong.

      comment.

    4. Re:Keep it up. by semi-extrinsic · · Score: 5, Informative

      Okay, so what are the kernel changes that users need? Filesystem - we currently have a choice of ext2, ext3 and ext4 - what's inadequate about any of them that couldn't be resolved in an ext5? Any reason why re-strippable RAID can't be in that?

      The general notion is that btrfs will "be" ext5 (i.e. it will be the next "updated" but still stable and mainstream FS), and that there will not be a filesystem with the actual name "ext5". For those who don't need btrfs features, ext4 will suffice. This is also the intent of Theodore Ts'o, the principal developer of ext3/4.

      I believe the reason for this is that the innovation going on in filesystems is centered around some big rethinks, e.g. btrfs uses a copy-on-write B-tree (a concept introduced in 2007). It would be a pain in the neck (or impossible) to innovate like this and remain backwards compatible with ext2/3/4, thus btrfs is not called ext5.

      One thing they could do as far as the Linux kernel goes is work on drivers - particularly Wi-Fi drivers, and do what's possible to ensure that 3.3, or 3.4 support just about every peripheral device there is out there. Aside from that, as far as I can tell, the Linux kernel is pretty much complete.

      How about you RTFS? To quote:

      There are also many small features and new drivers and fixes.

      --
      for i in `facebook friends "=bday" 2>/dev/null | cut -d " " -f 3-`; do facebook wallpost $i "Happy birthday!"; done
  2. C6X support is surprising by Anonymous Coward · · Score: 5, Interesting

    Wow, I had no idea there was work in porting Linux to DSP architectures. That's quite an interesting development. I wonder what the use case is, since DSPs are typically used for very specific, real-time work, not for hosting general-purpose operating systems.

    Also, it's quite surprising to me since as far as I know it's necessary to use TI's compiler to generate C6X code. I found one initiative to port GCC to it, but afaik it didn't get finished. My understanding is that it is no small job to get Linux to compile on non-supported compilers, so I'm interested in the toolchain they are using. For my own work on a C6711, I've been using the TI compiler under Wine. (Which works fine actually, although I had to generate an initial project in CodeComposer to get some of the board-specific support files.)

    1. Re:C6X support is surprising by macshit · · Score: 4, Informative

      Also, it's quite surprising to me since as far as I know it's necessary to use TI's compiler to generate C6X code. I found one initiative to port GCC to it, but afaik it didn't get finished. My understanding is that it is no small job to get Linux to compile on non-supported compilers, so I'm interested in the toolchain they are using.

      GCC 4.7 (which will be released soonish; it's basically already done) supports the C6X architecture.

      From the GCC 4.7 release notes:

      New Targets and Target Specific Improvements:
      ...
      C6X

      • Support has been added for the Texas Instruments C6X family of processors.
      --
      We live, as we dream -- alone....
    2. Re:C6X support is surprising by steveha · · Score: 4, Informative

      The TI C6X line of chips are not only VLIW, they are "DSP" chips, optimized for signal processing operations. Also, this chip has no MMU. Nobody is going to build a tablet computer or any other general-purpose device based on one of these.

      I think for the near term at least, anyone using a TI C6X will be using the TI C compiler. TI has a whole IDE, called Code Composer Studio.

      But now we have the possibility of running Linux on the chip.

      The one time I worked with a TI DSP chip, I didn't really have an operating system. Just a bootstrap loader, and then my code ran on the bare metal, along with some TI-supplied library code. Now I'm working with an Analog Devices DSP chip and it's the same situation. For my current purposes I'm not using any OS at all. But Linux support could potentially be great; for example, if you were using a platform with an Ethernet interface, you could use the Linux networking code; if you were using a platform with USB, you could use Linux USB code and file system code and so on.

      steveha

      --
      lf(1): it's like ls(1) but sorts filenames by extension, tersely
  3. Great timing by quantumphaze · · Score: 4, Funny

    I just rebooted to apply 3.2.11 :(

    1. Re:Great timing by MiG82au · · Score: 4, Informative

      Only thing I know of is Ksplice which is a private company that offered special run-time kernel patches. Oracle bought them out and no longer releases the software and the patches for free.

    2. Re:Great timing by gQuigs · · Score: 4, Informative

      I don't use linux, but I remember reading a while ago that linux introduced a feature to update the kernel w/o a reboot. Does this not apply?

      It's not built-in for any major distros yet. It's called ksplice, which is owned by Oracle now. (It is GPLv2)

      AFAIK it has not been mainstreamed.

    3. Re:Great timing by petteyg359 · · Score: 4, Informative

      Ksplice is just a commercial tool that makes use of kexec which has been in the kennel for years. There is absolutely no need for Ksplice yo use kexec.

    4. Re:Great timing by BitZtream · · Score: 4, Insightful

      Probably never will be either. Its usefulness was always questionable at best anyway, it is a GREAT academic exercise that I'm interested in just cause I've been developing my own 'x64 os' as a learning experience so the tactics they use I like to learn about, from a practical perspective as a system admin, its silly.

      Mission critical infrastructure where you would want continuous availability is running on a cluster which can stand to have a host rebooted for upgrades so live splicing kernels is pointless in those situations.

      ksplice is for people in moms basement who want an uptime long penis, not for anyone who actually needs service availability.

      ksplice is a treatment for a symptom, which has a long list of side effects that are non-obvious to your non-developer sysadmins, which means most.

      Clusters are the vaccination/condom that prevents you from developing the problem in the first place

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    5. Re:Great timing by Anonymous Coward · · Score: 5, Insightful

      Really?

      Well, explain this to me:

      When you have 8 servers each with 2 PCI-E Quad E1 Digium Cards, handling a total of 248 inbound calls on toll free numbers, with an average of 200 simultaneous channels per server 24/7, how do you cluster that? When you have analog CCTV cameras running into 4 servers each with 16 channels of video, well, how do you cluster that?

      Not everything is HTTP over TCP/IP. Not everything is easily solved with a load-balancing reverse proxy or DNS balancing/failover. Not everything can be clustered. In those situations, and I speak from experience (those two are real-life situations I deal with), not rebooting is real fucking important. And you have two options: either you leave systems unpatched and wait for the next 5 minutes downtime window that might be a year from now, hoping nothing bad happens, or you live patch those motherfuckers.

      If that wasn't enough, I can mention at least an extra 20 cases where clustering isn't an option, and neither is rebooting.

      The explanation is fairly simple. Your hardware does not meet the redundancy and failover requirements for the uptime expectations you've set. Equipment designed for extensive uptimes and critical services have built-in redundancy. Take your phone "server" for example. We run several types of phone service, and the one most similar to what you describe runs as a pair of servers, each with a primary and redundant connection. If either server fails, or if the connected switches/routers fail, they can failover to the backup hardware without even interrupting a call in progress. When we need to upgrade the servers, we do them one at a time.

      Rebooting always has to be an option. Always. Why? Because sooner or later you're going to have hardware failure, and you'll be rebooting whether or not you want to. Going with your 'head in the sand' approach only means your customers will feel a much greater impact from the inevitable downtime than they would if you'd properly designed your systems in the first place.

    6. Re:Great timing by Lost+Found · · Score: 4, Informative

      Not true. Kexec replaces the whole kernel, which means the system is reset. Ksplice applies and removes patches (security updates mainly) while the kernel is running, which means all the processes keep running as if nothing happened.

    7. Re:Great timing by batkiwi · · Score: 4, Informative

      "When you have 8 servers each with 2 PCI-E Quad E1 Digium Cards, handling a total of 248 inbound calls on toll free numbers,"

      This one is tricky if you're trunking with the local telco correctly. Your telco should offer a redunancy and rerouting service if you actually have 64 E1s with them.

      "When you have analog CCTV cameras running into 4 servers each with 16 channels of video, well, how do you cluster that?"

      That one's easy. Splitter before the capture card.

      If you care about it, it's capable of being made redundant.

    8. Re:Great timing by clarkn0va · · Score: 4, Funny

      Ksplice is just a commercial tool that makes use of kexec which has been in the kennel for years.

      HOO LET THE KERNELS AOT! WHOOT! WHOOT, WHOOT, WHOOT!

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    9. Re:Great timing by jimicus · · Score: 4, Funny

      Ah, slashdot. The place where you can indignantly call someone wrong because they've told you to do something that's impossible, only to have a whole bunch of people who've already done it explain that you, in fact, are the person in the wrong.

  4. Re:Great! by Daniel+Phillips · · Score: 4, Informative

    Features not marked "experimental" in the kernel config database are out of beta.

    --
    Have you got your LWN subscription yet?
  5. Re:Way to go....... by tpstigers · · Score: 5, Insightful

    Fanboism? Don't be a douchebag. This is a post about a new Linux release. The people who comment on this post should naturally be expected to be Linux users, probably fans. Just as a post about a new OS X release would naturally be populated with Apple fans. It's the people who purposefully comment on threads about products they DON'T like that create a problem. Then there are people like you who just enjoy acting like a dick. Give it a rest.

  6. Re:Which distributions? by Hardolaf · · Score: 4, Informative

    Arch Linux will probably support it in a few days. The packages have been marked outdated and there is already a 3.3rc7-1 ( https://aur.archlinux.org/packages.php?ID=50893 )release in the wild that will probably be the basis for the updated to 3.3.

  7. Re:Way to go....... by GmExtremacy · · Score: 4, Insightful

    It's the people who purposefully comment on threads about products they DON'T like that create a problem.

    I wouldn't say it's a problem. They, like to the people who like it, are simply stating their opinions.

  8. Re:Why Should I Care? by Anonymous Coward · · Score: 5, Funny

    You're just jealous that it'll take at least a month after Windows 8 comes out before somebody creates a Metro-style UI for X.

    Two to match the colors.

  9. Re:Which distributions? by quarkscat · · Score: 4, Interesting

    I cannot answer this question for any GNU/Linux distribution except for Slackware, which may or may not get Linux Kernel 3.3.xx as part of an official distribution for at least one Slackware release iteration ... But my personal Slackware machine will be getting 3.3 as soon as it finishes building and I reboot the machine. ;-)

    It's nice to have a GNU/Linux distribution that doesn't jerk users around with strange application locations, misaligned library versions, or an update schedule tied to commercial support contracts. I've tried the rest, and I returned to the best (imho), since GNU/Linux kernel 0.96. Don't try dropping a new kernel source tar-ball onto RH Enterprise Server, Fedora, or even Ubunto -- it will break your system, and your $$$$ support agreement.

  10. Re:Power Management by TheLordPhantom · · Score: 4, Interesting

    Mostly it is a problem with the video drivers. Especially AMD. The AMD open source drivers are horrendously inefficient. And, in my experience, the proprietary drivers aren't a whole lot better, but even worse, break everything. So I would say power issues are at the distribution level, not the kernel level.

  11. Anyone rebuilding their kernel still? by devphaeton · · Score: 4, Interesting

    Back in the Middle Ages (late 1990s through about 2004) I remember us all getting excited for new kernel releases, and then all rushing to download the source and build it. (By 'us' i mean myself and local geek friends, as well as our cohorts on various IRC channels).

    Nowadays with auto-configuring, rolling release desktop distributions being the norm, is kernel building now only done in server room environments and for non-PC hardware?

    This doesn't matter much, I'm just curious.

    --


    do() || do_not(); // try();
  12. Re:I suppose I have to start building... by Randle_Revar · · Score: 4, Informative

    It seems pretty clear stuff is not just being shoved in willy-nilly for android. There have been many debates about including this piece or that piece, and if the implementation should be identical to the android version. Many parts are not in yet, and some may not go in at all. The android suspending solution may not ever go in, mainline may eventually get a system that serves the same purpose in a different way, android may eventually support that. LWN and the LKML posts they link to give a pretty good overview short of reading all the code commits.

  13. Re:Bufferbloat by bytestorm · · Score: 4, Informative

    There isn't an easy answer to your question. In general, bufferbloat is when you get latency or jitter issues because some network device upstream of you has a large buffer, which it fills before it starts dropping your packets. The dropped packets is how software relying on TCP is notified of network congestion so it knows to throttle back. Other protocols may be affected differently (you might notice VoIP delay or bad lag on your xbox).

    To combat this, the idea is to limit your traffic in buffers you control which are (typically) smaller than your ISP and modem's buffers so the ISP ones stay empty and highly interactive. In general, this means limiting your data rates to lower than your bandwidth and prioritizing packets by interactivity requirements. The linux kernel additions in 3.3 allow you to set your buffer size smaller for the entire interface with the goal being to reduce the delay induced by the linux router/bridge. It also adds the ability to prioritize traffic and limit buffers by cgroup (which is like a process categorization or pool which has certain resource limits), but this isn't particularly helpful in your forwarding situation.

    For my own QoS setup, I usually use a script similar to this HTB one. It requires some tuning and getting your queue priorities right requires some understanding of the traffic going through your network. A lot of high level netfilter tools (smoothwall, dd-wrt, etc) have easier to use tools QoS tools which may better suit your purposes. Having not used one, I'm not in a position to recommend them.

  14. New "team" network driver by Elrond,+Duke+of+URL · · Score: 4, Interesting

    I am a bit confused with regards to the new team network driver which is going to eventually replace the current bonding net driver. The kernel newbies page says that it is user-space and uses libteam to do its work, but it also says that this new implementation will be more efficient.

    How is this so? As network throughput keeps increasing, it is important to process each packet as quickly as possible. That's why network drivers and the packet filter are in the kernel. Wouldn't moving the new team/bonding work to user-space mean a lot more data for the kernel to copy back and forth between kernel and user spaces? And wouldn't this hurt efficiency? I'm sure the computer can keep up in most cases, but it seems this will require more CPU time to handle the work.

    Just curious...

    --
    Elrond, Duke of URL
    "This is the most fun I've had without being drenched in the blood of my enemies!"-Sam&Max
    1. Re:New "team" network driver by Technonotice_Dom · · Score: 4, Informative

      The idea I believe is more that userspace is responsible for handling which device(s) are used for transmission and notifying the kernel, rather than being responsible for the sending of packets themselves. If you've got an active/backup bonding setup, it makes sense to perform connectivity checks from userspace which can be flexible and complex, then notify the kernel to switch or remove devices that have lost connectivity.

      The libteam daemon that's in development seems to have a round robin mode planned and I'd hope 802.3ad, but I guess we'll have to wait and see how that works. I'm sure it'll still need kernel support for the bonding implementations, it's just the monitoring and management functions that are being extracted.

  15. Re:Which distributions? by zill · · Score: 4, Funny

    5.5 kernel...

    This is either a typo or python is way more powerful than I thought.

  16. Re:Way to go....... by Anonymous Coward · · Score: 5, Insightful

    So... which part of this release actually provides a compelling reason to use Linux over any other OS?
    You've been itching for something to run on that TI C6X system you built?

    The fanboisim here makes me gag. Apple has nothing on you guys.

    Hey Cowboy did you know that the Linux Kernel currently runs most smart tvs, bd players, and other home entertainment devices. I would be willing to bet that the number of Samsung, Sony, LG and other tvs and devices running on the Linux kernel is much greater than the number of Macs, and PC currently in use combined!

    The reason for this is that any manufacturer can use OpenSource software like the Linux kernel and modify it to their own needs without sending money to Redmond for every device they sell. This is why Microsoft and Apple have failed in the embedded market with perhaps the exception of some car companies like Ford Motors. Ballmer can rant, rave and do all the paid shill crap he wants. Fact is as the kernel becomes more open to modification from companies like Google with Android optimisations and slick coding Microsoft will become irrelevant in many markets.

    The post was about the most important core software released in history so go pound on your PC, and post how linux sucks somewhere where someone cares. The Linux kernel is one hell of allot more that just the base of an OS as you perceive it.

  17. Re:Why Should I Care? by lattyware · · Score: 4, Informative

    That's rubbish. I have a triple monitor setup and KDE will happily let me make a panel 100% of any one screen, or 100% of all three (if you wanted to do that for some insane reason) at any orientation.

    --
    -- Lattyware (www.lattyware.co.uk)
  18. Re:Why Should I Care? by lattyware · · Score: 4, Interesting

    Well, it just seems highly unlikely that it wouldn't work for anyone else. I mean, it's a pretty basic feature and if I can do it with my pretty unusual and normally troublesome setup (triple monitors are not that well supported, although KDE does a good job), then I'd expect it to work with most people's. My point is, if it doesn't work for you, then it's a bug, so submit a bug report.

    --
    -- Lattyware (www.lattyware.co.uk)
  19. Re:Way to go....... by CSMoran · · Score: 5, Funny

    the android merge means i can play angry birds without having to use wine...

    Note that playing sober raises it to another level of difficulty.

    --
    Every end has half a stick.
  20. Re:Way to go....... by MrHanky · · Score: 4, Informative

    Bullshit. Not only does a merge of Android kernel features not mean you can play angry birds under some regular Linux distro (you'll need, oh, Dalvik and Android's windowing system which is not X11), you can already play Angry Birds in Chrome, no Wine required. The kernel is entirely irrelevant. If you don't know what you're talking about, just shut up.

  21. Re:Way to go....... by pegdhcp · · Score: 4, Insightful

    Then neither you are not working with web developers who change their mind daily about basic system design nor you are working in an environment where uptime is not a concern nor you have very expensive load balance boxen that protects you from mundane facts of life. Either way, you are a very lucky person... OTOH we, of lesser levels of humanity, are grateful for one more tool that would make our lives easier.

  22. Re:Why Should I Care? by Sique · · Score: 4, Informative

    According to my university lessons, the kernel and the drivers are the operating system, and everything else is shell and applications.

    MS Windows should thus be considered a distribution (combining OS, shell and applications and an install mechanism).

    --
    .sig: Sique *sigh*
  23. Re:Which distributions? by Barefoot+Monkey · · Score: 4, Funny

    Your problems with Slackware appear to stem from your use of the wrong mock-religion meme in your signature. Eris, in particular, is known to cause trouble. Try changing your signature to The Subgenius must have Slack and the package management should improve.