Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Facebook Joins Linaro Linux-on-ARM Effort

timothy posted about 2 years ago | from the like-a-tattoo dept.

Linux 60

dgharmon writes "It has been more than two years since Freescale Semiconductor, IBM, Samsung, ST-Ericsson, and Texas Instruments formed a non-profit software company called Linaro to help focus the disparate efforts to get Linux running well on ARM processors and system-on-chip designs. A slew of companies, some new to the ARM racket, have joined the Linaro effort – and as of Thursday afternoon, so has social media juggernaut Facebook."

cancel ×


Sorry! There are no comments related to the filter you selected.

Makes sense. (4, Informative)

cultiv8 (1660093) | about 2 years ago | (#41874699)

Re:Makes sense. (3, Informative)

hendridm (302246) | about 2 years ago | (#41874777)

FTFA: "Facebook and AMD are joining the Linaro Enterprise Group, which was formed to focus on "the development of foundational software for ARM server Linux," as the announcement put it."

Re:Makes sense. (1)

cultiv8 (1660093) | about 2 years ago | (#41874993)

can't figure out why I was modded down. ARM/Linux on smartphone makes sense, no? If someone can fucking tell me otherwise, great, still don't get why I was modded down for "redundant".

Re:Makes sense. (-1)

Anonymous Coward | about 2 years ago | (#41875707)

because it's in the fucking title dumbass. fucking nerds. you'd think they'd be smart...

Re:Makes sense. (0)

Anonymous Coward | about 2 years ago | (#41883509)

Smart nerds on slashdot are the exception rather than the rule. You'd think you'd be smart, dumbass.

Re:Makes sense. (1)

Anonymous Coward | about 2 years ago | (#41877713)

ARM/Linux on smartphone? Genius! Quick, call Google and Samsung and tell them about your amazing new discovery.

Re:Makes sense. (1)

MichaelSmith (789609) | about 2 years ago | (#41875253)

But there are so many working distributions out there right now, why start from scratch with a new one. For example there are about three linux based distros for the openmoko, all with custom UI front ends.

Re:Makes sense. (2)

rtfa-troll (1340807) | about 2 years ago | (#41878097)

There are about three linux based distros for the openmoko, all with custom UI front ends.

Most "distros" that you see are exactly that; ways of experimenting with different UI, usability and system administration concepts. The guys that do them don't want to do much of the low level plumbing. Think of Linaro as being similar to Mer [] which is the underlying developer whilst Plasma Active [] and Nemo [] the consumer distros built on top of it.

In the case of Linaro, though, they are trying to support completely embedded customers. These users often don't end using a proper distro at all. For this reason Linaro is less building a distro that people build on top and more building examples of working systems people can copy from. Let's say you are an SOC or sensor vendor that wants to sell to Android vendors in future. Your first place to start would be cooperating (paying) Linaro to get it working. Once that's done, everybody can can see how it works and is confident that they can also get it working in their own build of Android. At the same time you get access to the massive embedded Linux market.

This is one of the ways in which modern community oriented FOSS software works a bit differently from proprietary software. You see all of these experiments and development versions out in the open where each of them would be hidden somewhere deep inside Microsoft's R&D. For the hardware company this is a great way to address all the different Linux distros via one place. For the Linaro guys this is great because they continue to get the latest hardware to develop on all the time and they don't need to stop working and integrate to other distros. For the developer this is a great opportunity to understand which hardware will be best supported in future. For the normal user the message is "don't worry be happy".

Linaro is not *a distribution* (1)

DrYak (748999) | about 2 years ago | (#41880647)

Linaro is not a distribution. It's a joint effort to *help linux run on ARM hardware*.

For example there are about three linux based distros for the openmoko, all with custom UI front ends.

And for these "linux based distros" to work you need a running linux (kernel) on which to base them. That's the work of the software company named Linaro.

To give into more details:
as a point of comparison, in the x86 processor world, things are rather standardized, and well modularized. There's more or less only one single main platform (the PC) with some weirder variant (BIOS vs. (U)EFI, or even weirder PC vs. custom Apple Intel Macs) and a few exception (they are really rare and don't matter much for mass consumption). With clearly organized components (no matter if you go for Intel, AMD, Via or more rare hardware: you've got the same basic CPU, northbridge, south bridge, PCIe bus, etc.). And well defined procedure to initialise and control everything. On the software side, all this is controlled by using clearly modularized and segregated components.
When something new arrive to the market (like the jump from BIOS to EFI, the move from PCI to PCIe, etc.) you only need to write a module and leverage what already exists for everything else.
To boot into linux, you use the same kernel everywhere, and only load different drivers depending on the local variations.

in the hardware arm world, things are much more messy: lots of weird SoC are put together, with far less standardisation. Also, whereas the x86 hardware is general purpose and widely available to everyone (just think about all the beige boxes everywhere. Then think that if you need server, a compute node or a home theaterPC you use the samecomponents. And branded machine (brand servers) use the same componenents too), lots of the ARM hardware tend to be put together for very specific custom usage (a company using their own SoC + PCB for a router. Another for a smart phone. Another for a NAS. Another for TV set top box. Etc.). Lots of this hardware is one-shot (there's few design re-use between a router and a smartphone).

as a consequence, before Linaro, Linux on ARM was a big mess: each time a company put together some hardware, they also do their own port in a one-shot fashion: they download the linux source, write a big monolithic patch to support their own weird variant, compile it, even sometimes publish the code (to be compliant with the GPL) and call it a day.
when another company wants another ARM-based machine, they just to the same.
No modularisation. No code re-use. No easy rebasing of the kernel.
That's why for several pieces of hardware, you're basically stuck with one very specific kernel version (openmoko is still at 2.6.x something) even when the source is available: the hardware depends on a huge monolithic platform drivers which is tighly dependant on the very specific kernel version against which the patch was written.
If there's any known kernel bug, your only hope is to wait for the back-port. you can't just move to a recent kernel (to 3.6.x).
If you want to provide a distribution for several pieces of hardware, you need one separate kernel per each separate device, sometimes different kernel version (depending against which kernel version was the patch written).
A big mess.

It's not a surprise that Microsoft is having big difficulties with Windows 8 on tablets and smartphones: the hardware landscape is really weird (and their own approach is to impose 1 single specific type of platform, so writing Windows 8 is easy and have everyone else standardize on it) (that's why they won't end up being as much popular on smart phone as they wished).

The role of Linaro was to put some order in this mess, by gathering together several of the people involved (there are hardware companies here) and giving them opportunities to work together and coordinate their effort. Among them as well as together with the kernel developers and the rest of the community.
Split everything into small component which will be easy to re-use (for newer slightly different hardware) or re-base (new kernel = keep as much of the drivers as possible). Organise everything cleanly.
The target: to achieve the same situation as with x86 hardware - same kernel everywhere, all the magic lies in modules and component. Re-using should be easy and cheap (just write new drivers for the new hardware elements, re-use as much as possible from the rest. Or even write a new batch of settings for a generic driver). Everything should be as modular as possible, and get everything possible back into the official kernel (no monolithic patches).
The end users see benefits (they get better quality of code, and longer maintainability. This requires open source code, but also require code which is easy to work with. The past mess wasn't. The future for which Linaro strives is).
The hardware makers see benefits (the initial cost of developing new embed hardware is lower, no need to write full monolithic patches, leverage as much as possible from what already exist. The overall development/maintenance is also simpler: no need to keep one separate kernel for every piece of hardware poduced, and easier to get updates from the mainline kernel).
And the kernel developing community see benefits (easy to keep and maintain modules in the mainline kernel, less headache when big changes arrive with newer kernel as everything is nicely modularized).

If today you start seeing interesting distros on ARM (lots of smartphone-specific distros. big name distros like Ubuntu and openSUSE. etc.) that's exactly because of the work behind the scene of developers like those from Linaro, making the Linux kernel easy to make work every where.

Re:Makes sense. (0)

Anonymous Coward | about 2 years ago | (#41880109)

*facepalm* No, it makes sense if you're Michael DAMN I NEED AD REVENUE Arrington., or one of his gullible readers.

"How do I get hits? People barely care about the latest doohicky, and I've already written 40 stories about the iphone 5 this week! Is it too soon to talk about the iphone 6? Any leads on the iphone7?"
"Hmm...looking at Google trends shows that alot of people type in to go to the website, and a lot of various searches for cell phones".
"Holy shit! I've got it! Facebook is going to make a cell phone! Hurry and photoshop a facebook logo on any blue colored phone you can find! My adsense revenue is going through the fucking roof this week"

That's just how Michael Arrington rolls.

There's never been any proof that Facebook has been working on a cell phone. They've worked on apps and compatibility, and for obvious reasons. HTC provides some substance to the rumors by releasing cell phones (HTC Status, HTC ChaCha) that provide "deep Facebook integration", like a button with a F on it.

Of course, don't take my word for it

Um... (1, Redundant)

epp_b (944299) | about 2 years ago | (#41874719)

I'm posting from a Linux on ARM device right now.

Re:Um... (-1)

Anonymous Coward | about 2 years ago | (#41874745)

No you're not.

Re:Um... (0)

Anonymous Coward | about 2 years ago | (#41880285)

Grade school troll. I award you no points, and may god have mercy on your soul.

Re:Um... (5, Informative)

godrik (1287354) | about 2 years ago | (#41874755)

Of course, that's not what Linaro is about. They are looking forward to stop the explosion of code and architecture within the ARM familly. No two ARM machine boots the same. No two ARM processors expose component the same way. You did not read Linus saying "what about stoping the ARM crap?" []

Re:Um... (0)

hendridm (302246) | about 2 years ago | (#41874801)

Of course, that's not what Linaro is about. They are looking forward to stop the explosion of code and architecture within the ARM familly.

Agreed, it even says that in the summary, lol.

Android? (0)

Anonymous Coward | about 2 years ago | (#41874857)

Isn't Android itself a Linux-derived OS? I thought Torvalds said that Android will be converging back to Linux in the future.

Re:Android? (2)

Gaygirlie (1657131) | about 2 years ago | (#41875089)

Isn't Android itself a Linux-derived OS? I thought Torvalds said that Android will be converging back to Linux in the future.

Yes, Android runs on a slightly modified Linux-kernel. Most of the modifications have now made their way into the mainline kernel, so in the future it may well be possible that there is no need for modifying the kernel at all. The userland on Android and any Linux-distro is entirely different, but I s'spose you knew that already.

Re:Android? (1)

Johnny O (22313) | about 2 years ago | (#41877955)

Android runs ON Linux. end of story... Including all the utilities unix/linux provides. It is a Linux distribution that relies on Java for the desktop. SuSE, Slackware, and RedHat are based on Linux. They have different desktops based on different technologies.

They are all Linux.

Re:Android? (0)

Anonymous Coward | about 2 years ago | (#41878233)

What part of "the standard linux kernel cannot run Android" do you not understand?

Any distro's userland can run on most any standard linux kernel, except for Android's userland.

There are big steps being taken to amend this situation, but we're far from "there" yet.

Re:Android? (1)

Gaygirlie (1657131) | about 2 years ago | (#41878341)

Android runs ON Linux. end of story... Including all the utilities unix/linux provides. It is a Linux distribution that relies on Java for the desktop.

Incorrect. Taken from the Wikipedia - page for Android:

Android's linux kernel has further architecture changes by Google outside the typical Linux kernel development cycle.[43] Android does not have a native X Window System by default nor does it support the full set of standard GNU libraries, and this makes it difficult to port existing Linux applications or libraries to Android.[44] But the support of simple C and SDL applications is possible by injection of a small Java shim and usage of the JNI[45] like e.g. in the Jagged Alliance 2 port for Android.[46]

Re:Android? (0)

Anonymous Coward | about 2 years ago | (#41878613)

Android patches to the kernel are merged with the mainstream Linux kernel. The reason it can not run certain Linux applications is purely userspace related: the C library. Android uses Bionic instead of GLIBC. You have the same issues when you would run uCLibC on an embedded target. It's still Linux... Also, JNI is not the way forward to develop C applications on Android anymore. The NDK is there for that purpose. For all intents and purposes, Android is Linux. The userspace might be different, but that's the same with every other embedded Linux device out there...

Re:Android? (1)

Gaygirlie (1657131) | about 2 years ago | (#41878847)

So, you're saying the exact same thing I said?

Re:Android? (0)

Anonymous Coward | about 2 years ago | (#41878727)

X windows is not Linux. GNU libraries are not Linux.

I port utils to android on Bionic (the slimmed down GNU libs).

Works just fine for Google to run ls/mount/fsck/etc. Works for me.

Android runs on Linux. The Linux kernel.

Re:Android? (1)

Gaygirlie (1657131) | about 2 years ago | (#41878891)

I don't get your point? You're just saying the same thing as I said?

Android convergence vs. Linaro (1)

DrYak (748999) | about 2 years ago | (#41880893)

The Android convergence was about bringing the specificities needed to run android userland back into the main kernel tree, instead of a special separate fork.
(e.g.: Among other, Android uses some special type of IPC)
Since recent kernel (was it 3.5? 3.6? memory fails me) these modifications are back into the main tree.
So, today, *as long as the hardware is supported*, you can run Android using any modern kernel. (for example: there are some interesting experiment of having both Ubuntu and Android running on the same ARM device using the same kernel)

Linaro is about the rest, about the "as long as the hardware is supported" part. As said above by godrik:

No two ARM machine boots the same. No two ARM processors expose component the same way.

As I've explained elsewhere in this topic [] , this has lead in the past to a situation where every single ARM machine has a seprate monolithic patch which was custom-written in one shot by the machine maker.

The point of Linaro is to bring some discipline in this, bring cooperation between all makers & developpers, and help modularize all this into small independent component.
So when the next machine comes to the market, instead of writing yet another new monolithic patch completely from scratch, as much work as possible can be leveraged from what already exist.
And the other way around: when a new kernel version comes, instead of having to port several thousand different monolithic patches (which never happens. end-users are always stuck with hardware specific versions), it will be easier to just maintain the few modules affected by the update changes.

When both are combined, that means it'll be incedibly easy to use Android on as many devices as possible. For the manufacturer, that's a no-brain choice. The mainline kernel contains everything needed to run android, and contains a lot that can be leveraged to support the hardware. Either write just a few new needed drivers, or even better (if you're lucky) only write new settings for some generic hardware.

BTW: Microsoft has chosen a different path - screw everything else, we're only supporting one specific way, one single type of machine. Either go our way, or pick another OS. My bet is that this isn't going to work very well, specially given the flexibility that android is offering on the other hand.

Zoos are Expensive (1)

mrbluze (1034940) | about 2 years ago | (#41875899)

Of course, that's not what Linaro is about. They are looking forward to stop the explosion of code and architecture within the ARM familly. No two ARM machine boots the same. No two ARM processors expose component the same way. You did not read Linus saying "what about stoping the ARM crap?"

Soon they will have to address this problem, not so much as to allow Linux to spread, but because it drives the cost of ARM based devices for the companies that make money writing the operating systems for them, such as Microsoft. It is a competitive disadvantage for ARM to be in charge of a zoo.

Re:Um... (0)

Anonymous Coward | about 2 years ago | (#41874837)

If you we're running Linaro you would have made it to first post!

Re:Um... (1)

cultiv8 (1660093) | about 2 years ago | (#41875059)

...and you were modded down as redundant for saying this... same as I was.

Stealing Credit (0)

Anonymous Coward | about 2 years ago | (#41874731)

I'm pretty damn sure Linux worked quite well with ARM long before this group decided to pretend that they invented everything. Apple, much?

Re:Stealing Credit (0)

Anonymous Coward | about 2 years ago | (#41874833)

Yeah, I jailbroke my iPod one day and installed a custom distro on it. To hell with developing standards and furthering the cause!

Re:Stealing Credit (3, Informative)

Elbereth (58257) | about 2 years ago | (#41875009)

According to the Wikipedia article [] , these guys are simply trying to simplify, optimize, and reduce fragmentation in the ARM/Linux world. They're not trying to claim anything except that their tools and validation suite make your life easier.

It's sort of like the Linux Standard Base, if you remember that initiative. The LSB was invented to address concerns of fragmentation and difficulty in porting applications to Linux, because the distributions were so radically different from each other. While it didn't work out as well as hoped, it did manage to reduce the idiosyncrasies.

Re:Stealing Credit (2, Informative)

Anonymous Coward | about 2 years ago | (#41875137)

For that matter Linaro has been making ARM patchsets for various hardware for over 10 years (maybe even longer!). Probably 3/4 of the ARM Linux hardware you'll find (be it routers, IPCams, print servers, etc) will be running some kernel with a -linaro in it, and even the ones that aren't usually have a -linaro in the gcc/binutils buildversion.

They're just trying to reduce their own costs by consolidating the majority of necessary changes into patchsets that will be accepted into the kernel, so that minimal additional, potentially conflicting, code will end up outside of the kernel in the long run.

Can't fault them for wanting to make both our and their lives easier.

Re:Stealing Credit (2)

rdnetto (955205) | about 2 years ago | (#41877417)

For that matter Linaro has been making ARM patchsets for various hardware for over 10 years (maybe even longer!).

Citation needed. According to wikipedia, Linaro was only founded 2 years ago.

I don't get the non-profit part (0)

Anonymous Coward | about 2 years ago | (#41874843)

So from what I've heard, each participant has to pony up some nontrivial amount of $ and people. Where's all that money going?

Promote (0)

pkbarbiedoll (851110) | about 2 years ago | (#41874873)

Now Facebook can promote posts and move its important news, links and photos higher on Slashdot's news feed. This post will be marked as Sponsored. Enter your Facebook corporate P-Card details below.

" to get Linux running well on ARM processors" (3, Informative)

Gaygirlie (1657131) | about 2 years ago | (#41875001)

I guess it depends on what you mean with "running well": I have a Pandaboard and, well, it has been a major clusterfuck all the way from the beginning, what with constant breakage of features, on some releases of the software the features disappear completely, and then there's the constant crashes in the kernel. Imagine my surprise when I installed the latest stable Texas Instruments - release of the kernel only to find that networking is completely broken and the kernel goes to a hard lock-up after being on for 5-10 minutes, whether or not it just sits idle this whole time.

If all I want out of it is unaccelerated X or just console applications then yes, it runs very well, and it works great as a low-foothold server for all kinds of things. I'm just saying that I sure have no high expectations for these guys and their efforts.

Re:" to get Linux running well on ARM processors" (2)

rdnetto (955205) | about 2 years ago | (#41877491)

The very reason it's a clusterfuck is because of the fragmentation these guys are trying to address. Each device has a different kernel, even those that use the same SoC (because the GPIOs, etc. are hardcoded). That means that the developers efforts are fragmented - only a small number of people see the bugs and put in the effort to fix them, which undermines Linus' law. 3.7 [] will help, but there's still a lot to be done before ARM has the kind of compatibility that x86 does.

tldr: These guys are doing useful, important work that will vastly improve the state of Linux ARM.

Re:" to get Linux running well on ARM processors" (1)

drinkypoo (153816) | about 2 years ago | (#41879353)

I'm sorry to hear your Pandaboard is a clusterfuck, but the Raspberry Pi is pretty stable now so long as you don't try to use turbo mode so clearly it's not impossible to get something working.

Personally I only know linaro exists because someone compiled an advanced kernel for the Nook Simple Touch with it, and it's supposed to have improved performance considerably. I can't speak to that, because this kernel also provides a lot of other things including overclocking, and I didn't even try to make a direct comparison. But, if they've optimized gcc to make better ARM code, they have made me happy.

ARM servers (2)

symbolset (646467) | about 2 years ago | (#41875345)

It's long past time for this. China is doing MIPS servers too.

Not About Mobile (4, Interesting)

fm6 (162816) | about 2 years ago | (#41875371)

Even if Facebook is planning a smartphone (huh?) they don't have a lot of motivation to improve core Linux on ARM. I think it more likely that they're seriously looking at transitioning their (huge) data centers to ARM in order to save energy costs.

I've poo-pooed ARM-server speculation in the past, but this goes way beyond speculation.

While you are at it (0)

jfdavis668 (1414919) | about 2 years ago | (#41875517)

Can you get Linux to run on a 6502? Thanks.

Re:While you are at it (1)

sensei moreh (868829) | about 2 years ago | (#41875877)

My first personal computer had a 6502 (and a Z80) on the motherboard. Now get off my lawn!

Re:While you are at it (1)

Rhinobird (151521) | about 2 years ago | (#41876055)

Ah...I still have fond memories of my C=128

Re:While you are at it (2)

rubycodez (864176) | about 2 years ago | (#41876589)

no, it has no MMU

Re:While you are at it (0)

Anonymous Coward | about 2 years ago | (#41877733)

MMU is not a requirement for the Linux kernel to run.

The real problem is that it is an 8-bit CPU. Linux requires a 32-bit CPU to run.

Re:While you are at it (1)

rubycodez (864176) | about 2 years ago | (#41897209)

there are the ARM patches to 2.6.14 t o 2.6.19 work on an MPU (Memory Protection Unit rather than MMU) of certain ARM systems

so, you need something to manage memory
and ucLinux is not Linux

Re:While you are at it (1)

serviscope_minor (664417) | about 2 years ago | (#41879737)

no, it has no MMU

Actually, that's not the big problem. I think that the MMUless code was merged back into the mainline at some point. Either way there's still ucLinux.

The more fundemental problem is that the stack pointer can't be moved, which makes preemptive multitasking painful.

But it has been done, and it's called lunix.

Re:While you are at it (1)

rubycodez (864176) | about 2 years ago | (#41897059)

ucLinux is not Linux

Re:While you are at it (1)

rubycodez (864176) | about 2 years ago | (#41897231)

also, the ARM patches to a few of the 2.6 kernels that use the MPU of certain ARM systems still is relying on a memory management/protection hardware

no memory management/protection, no full Linux

Re:While you are at it (1)

UnderCoverPenguin (1001627) | about 2 years ago | (#41885729)

Emulate an x86 or supported ARM on a 6502. Of course, performance would likely be seconds (or minutes) per FLOP. Aside from the slow instruction cycle rate of the fastest made 6502, all your "emulated" RAM would have to be on disk.

now only if facebook could... (0)

Anonymous Coward | about 2 years ago | (#41876415)

Work to make sure their mobile app doesn't blow chunks on a certain linux based os that runs on arm....
Seriously, the android version absolutely blows compared to the iOS version. You're better off just opening your browser and hitting up

Downsides to running ARM servers? (1)

AlphaWolf_HK (692722) | about 2 years ago | (#41876499)

I understand the upsides of ARM servers, namely lower cost hardware and much better energy efficiency. However, what are the downsides? I've heard mixed stories about whether or not we can achieve the same performance from ARM as we can from x64, but nothing concrete.

If there are no significant shortcomings, I'd wager that Intel's days are numbered. A lot of AMD's revenues come from server deployments, and they've already jumped on board with ARM, but Intel shows no interest in doing so. You'd figure that *maybe* intel would license its architecture similar to how ARM does, rather than keeping everybody else out except for AMD through cross patent agreements, in order to keep x86 alive, but they don't show interest in doing that either.

Sure there's always the desktop market, but that segment is seeing very limited growth at the moment, and there aren't any indications that this will improve any time soon, especially with Microsoft and its apparent plans to push everybody over to architecture agnostic applications (although, whether or not that will succeed depends on who you ask.)

Re:Downsides to running ARM servers? (2)

imsabbel (611519) | about 2 years ago | (#41876555)

Server chips make less than 12% of AMDs revenue, tieing with chipsets, of all thing. Graphic chips are more than twice that.

Re:Downsides to running ARM servers? (1)

sky770 (2731643) | about 2 years ago | (#41877497)

ARM is the future. Period. Atleast for the mobile segment and for those who want to cut down development costs, save on energy efficiency and on top of all that "increase in processing power" ( LOL din't I just covered every "major" aspect of the needs of our immediate future?) More and more ARM SoC's are having better and better GPU's in them which are coming up quite well. Also, you should have a look at the Adapteva's Kickstarter Project Parallella [] . Its based on a dual-core ARM A9 SoC. Now this might spark enough ideas to convert this baby into a ARM based server..idk for what not but it'll be cool enough for scientific applications.

Re:Downsides to running ARM servers? (1)

banbeans (122547) | about 2 years ago | (#41877583)

It really depends on the load.
I don't see them taking over totally anytime soon but for some tasks they will be good enough.

sql back end of any kind forget about it, not even worth discussing anytime some.
They could need hardware accelerators to even be really useful on anything but the lightest loads.

Even middle-ware processing, not soon.
This is an area where accelerators could shine.

Front end web servers, This is the place they will show up and shine.
A lot of power is wasted waiting to serve a heavy load that only comes a few hours a day.
The small standby power of ARM is a good start. Get the i/o up and add some accelerators.
Hook them up to a fast fabric and go.

File servers are a real possibility many NAS already are running them, but they don't scale yet.
They do have the potential to do so however if the r&d is spent on them.
Many raid controllers are nothing but lower end arm cores running firmware, put 5 or 6 of these on a single chip with some fast 64 bit cores to run the OS and a 10GB network controller on a fast fabric and you would have the basis of a killer server.
Routers, many already are ARM and they will scale farther up the food chain in the future.

Re:Downsides to running ARM servers? (2)

drinkypoo (153816) | about 2 years ago | (#41879373)

It remains to be seen if ARM will ever offer the same single-thread performance as x86, but it offers better performance per watt now, so embarrassingly parallelizable tasks are already better done on ARM so long as the servers don't cost so much that you don't save any money using less power. Power is pretty expensive these days though, which is one big reason you're seeing so much interest in ARM servers, and intel isn't exactly known for offering their chips at unbelievably low prices.

Re:Downsides to running ARM servers? (0)

Anonymous Coward | about 2 years ago | (#41880493)

Intel _had_ ARM licenced - and sold out to Marvell most of its line. If you can get 32 ARM cores @5W each running at the same power / cooling cost as a 2 CPU Xeon - 8 Intel cores - you may get a useful server for webhosting / some virtualisation / email account hosting or whatever - or just getting oodles of processors in one 48U rack for bulk data processing. And that assumes that you can _only_ get 32 cores in one 1U server and that they take the same amount of cooling (typically, the cores run at 2-3W flat out and cost less to cool accordingly)

Course, core to core on the same die is easy - data throughput to disk/SSD/network is proportionately harder ...

Re:Downsides to running ARM servers? (0)

Anonymous Coward | about 2 years ago | (#41888685)

Besides price & per-thread perf (which isn't needed for the Web anyways): Compatibility. People stuck on Windows Server tech (which won't go ARM) such as Active Directory, IIS, SQL server, etc can't move unless they throw out their software & knowledge on how to use it. That's not going to happen for power efficiency sake in businesses without dedicated IT departments. But now small businesses are going to "Cloud Apps", so there may be less of that then I think.

Here comes the.. (0)

Anonymous Coward | about 2 years ago | (#41877469)

Isn't El-diablo means the "devil" ?

No. (-1)

Anonymous Coward | about 2 years ago | (#41877883)

Get your Linux off of my Windows 8 tablets.

Check for New Comments
Slashdot Login

Need an Account?

Forgot your password?

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>