Earlier quoted context omitted.
IME majority of linux systems are laptops and desktops.
at least inside docker or wsl
Docker wouldn’t be affected by this, the network stack is lower. WSL would, however.
Reworking 30 lines of Linux code could cut power use by up to 30 percent
41–50 of 123 posts
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#42> The code has been implemented as part of the Linux kernel release version 6.13 in January. This is basically 3 month old news now.
I'm one of the lucky 10,000.
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#43Earlier quoted context omitted.
Agree. On reading the headline, I was hoping it would extend my laptop battery life.
Same here, I have used Linux as my main for a long time. Though, I would imagine that data centers do have more instances than the desktops and laptops around the world combined.
And another one here!
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#44[dead]
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#45Earlier quoted context omitted.
It’s a lot more nuanced than that. Being in a data center doesn’t imply heavy network utilization. The caveat is clearly outlined in the article being workload based not deployment based. If you have a home machine doing network routing it would absolutely benefit from this. In fact I would say probably the vast majority of Linux installs are home network devices, just people don’t know it. Embedded Linux machines do…
I was curious how much this would be applicable to home routers. I confess I'm dubious on major savings for most home users, though? At least, at an absolute level. 30% of less than five percent is still not that big of a deal. No reason not to do it, but don't expect to really see the results there.
Practically none of it would be applicable (if using a commercial router). They all use hardware offloading, and traffic seldom touches the CPU. Only "logical" tasks are raised to the CPU, like ARP resolution and the likes (what’s called "trap to cpu").
If you’re doing custom routing with a NUC or a basic Linux box, however, this would gain massive power savings because that box pretty much only does networking.
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#46Earlier quoted context omitted.
IME majority of linux systems are laptops and desktops.
Without looking at stats, I would think android phones.
Android isn't Linux. While Android uses the Linux kernel, it's not a standard Linux distribution. It has its own user space and libraries, making it a distinct operating system.
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#47Earlier quoted context omitted.
It’s a lot more nuanced than that. Being in a data center doesn’t imply heavy network utilization. The caveat is clearly outlined in the article being workload based not deployment based. If you have a home machine doing network routing it would absolutely benefit from this. In fact I would say probably the vast majority of Linux installs are home network devices, just people don’t know it. Embedded Linux machines do…
What home router would be busy polling?
Someone who decided to turn their old PC into a router because a youtube video daid "recycling" an old PC is more green despite the massive power suck.
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#48This brings back memories.
https://didgets.substack.com/p/finding-and-fixing-a-billion-...
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#49I thought that Intel added the ‘pause’ instruction to make busy spinning more power friendly
Re: Reworking 30 lines of Linux code could cut power use by up to 30 percent
#50Oh, as a guy which was using DPDK like technology that do busy-poll and bypass kernel to process network packets, I must say may be much power have be wasted...
Standard practice in all trading applications is to busy poll the NIC using a kernel bypass technology.
Typically saves 2-3 microseconds going through the kernel network stack.