Originally posted by Master5000
View Post
Announcement
Collapse
No announcement yet.
Google Fixes A Longstanding, Important TCP Bug In The Linux Kernel
Collapse
X
-
Hmm. This bug reminds me of another (inherent?) flaw in the typical Berkeley socket implementation. When you close the socket, all pending outgoing data is immediately destroyed, and nothing is send (the expected behavior appears undocumented). This requires the client application to wait for the network stack (networking hardware mostly?) to finish up, wasting lots of CPU cycles. My guess is that Google & co have custom socket implementations or hardware that have this fixed (or worked around), but for your typical client application (read: everything not in a datacenter), you have to wait until it burps. An enormous amount of energy must be wasted worldwide on those pointless CPU cycles.
What I learned is that the technology that powers the internet is extremely fragile, outdated, and quite frankly, in very very poor state. OpenSSL/Heartbleed was just the tip of the iceberg. IMO, it's a miracle that things just work at all.Last edited by Remdul; 28 September 2015, 09:48 AM.
Comment
-
Originally posted by vsteel View Post
Zork> Pick up sword.
Zork> Kill troll with sword
The troll is disarmed by a subtle feint past his guard.
The unarmed troll cannot defend himself: He dies.
Almost as soon as the troll breathes his last breath, a cloud of sinister black fog envelops him, and when the fog lifts, the carcass has disappeared.
Your sword is no longer glowing.
Comment
-
Originally posted by Master5000 View PostIf these issues are longstanding bugs in the kernel then I don't think Linux is serious OS. It's probably better that it's at 1%.
Comment
-
Well, I noticed some strange "oscillations" in TCP traffic, too. And I suspect this could at least partially mitigate it. Though calling it "important" is overrated: it only happens in very specific circumstances and does not affects most of users most of time. So after fix, most people would not see anything changed at all...
Comment
-
Originally posted by FLHerne View PostOn web servers - where this is actually relevant - that share is more like 70%. More than twice that of Windows.
Comment
-
Originally posted by Rexilion View PostBesides, from the description it seems that the issue goes away once the first congestion is detected and acted upon accordingly.
Comment
-
Originally posted by FLHerne View Post
On web servers - where this is actually relevant - that share is more like 70%. More than twice that of Windows.
I think that windows has something like ZERO percent share in portable devices.
I actually think that this bug will have more impact on portable devices than servers. Because servers tend to have multiple users, they don't generally have a quiescent period. They stay under load. Portable devices, on the other hand, have the OBJECTIVE of maximizing the quiescent periods in order to improve battery performance. So they'll sit there dormant, until they blast everything all at once. Combine that with a generally SLOWER network, and bad things happen.
Comment
Comment