Because the RSB is shared among hardware threads that execute on the same virtual processor, this pollution enables inter-process, and even inter-VM, pollution of the RSB.
Well I guess there is a reason OpenBSD folks did this:
If it requires hyperthreading, how are ARM chips affected, and I assume in this case then only the Ryzen chips from AMD would be affected, since older AMD chips had no hyperthreading?
I can only assume that Cisco has moved on from selling to the engineering teams to selling to the c-suite. That's the only explanation I can come up with for a company with multiple back-doors found in their products still being able to make sales.
Cisco has always made buggy crap. The only reason they have been working at all is because they have been industry standard so all the little players had to work around Cisco's bugs.
If your operating system was programmed well, the IO call writing to the USB drive would not return until all write buffers were flushed, would not permit large write buffers to a USB drive -and- nothing else would attempt to write the USB drive in the background.
Your operating system was not programmed well. Quick Removal only gets close.
That is bloody stupid. That is how you get 1980s IBM PC floppy performance.
To get any kind of halfway decent performance you need asynchronous IO, otherwise you can't read one place while writing another, and while updating the UI.
Was the Amiga able to sense a floppy is in the drive? PC floppies can't - the floppy controller doesn't even know if the drive is present or not, so if you disconnected your floppy drive (or the BIOS wrongly said there's one) you got a ghost drive in Windows.
If only modern operating systems had such technology.
They seem decent at warning that writes are ongoing on USB media
Yes, it could even tell which floppy you put in. Each individual floppy got a separate drive name, so it could ask for data on specific floppies, and have it automatically work if you installed extra drives and put some floppies there (you could even upload a floppy to memory, and games would use it automatically).
They already build two laptops — three if you count the Air. They already have a pro and non-pro laptop line. The problem is that they have no clue what pro users want. If that were not the case, they would have acknowledged the feedback from 90% of users that the touchbar is a false-triggering nightmare of epidemic proportions, and they would offer an optional normal keyboard.
I too had stability issues with the K6... It turned out it was related to the VIA chipset, and more specifically the drivers.. Not that they were buggy, no no, they failed to handle buggy 3Dfx, buggy NVidia and buggy Soundblaster hardware that were all violating the PCI standard, and when you had two of them (which most gamers had), there were small but non-zero chance they would step on eachothers toes due to their abuse of the PCI standard and fuck the system state up.
The non-VIA drivers and Intel BIOS all had work-arounds to keep those buggy hardware in check. After the issue was fixed in a VIA-driver update, there were no more crashes.
But as often is the case. The blame lied nowhere close to whom most people blamed.
The purchased company always pays for the acquisition nowadays, and the sooner the better.
A common strategy is to have the company you just purchased take out a bunch of debt in order to pay you back for the honor of being owned by you. They are then responsible for paying the debt back, while you walk off to the bank with your profit up front.
Depends on the level. A more typical one is to issue more shares and pay with those shares, and at the same time make one-tme bonuses to the now redundant CxOs who negotiated the buyout or merger.
Since the top management are typically not the major share holders unless they are founders, this is the best way for them to ehm.. acquire a bigger share or companies or just huge piles of cash. The whole thing is inexact enough in valution that you can extracts billions that way.
well no - that pays for the acquisition cost - what's needed now is new revenue...
You never need to pay for acquisition. Unless you destroy the companies you buy, they pay for themselves in that it makes your company's net worth increase by what you paid.
The only point you would need to pay for it, is if you mess it up, and end up writing it off, but that is pretty rare.
I have a 32GB Android phone and Google apps consume less than 500MB of space (including updates which still leave built-in apk files intact - that's the only way to provide safe and secure factory reset and revert to the original apps if their new versions misbehave).
Must be a magic phone. I have 16GB phone and the mandatory google apps take up 10+GB or space.
C++ is so big/complex/rich that different people or groups use different subsets, from 'better ANSI C' to 'Object hierarchies everywhere with lots of templates.' I've seen code that obviously started as "my first OO project" with classes including copy constructors and getters/setters for the most primitive structures that were later changed with basic C code and friend declarations so that this code could work around the class structure. And a bit of STL here and Boost there.
I only know three common subsets: - Industry standard - No exceptions or RTTI, used by Apple, Google, Qt, KDE, and Microsoft. Is currently limited at C++11 or C++14 depending on project. - Kernel safe: Mostly C with some nice syntax things and a few templates, used by GCC and various low level libraries and hobby kernels. - Language wanking - Uses everything, used by the STL, Boost, and newbies.
Every language has a set of idioms that works and C++ is no exception.
There are just more of them in C++ and the language is designed to be able to handle new ones with ease. Still newbies shouldn't be doing that, which is one of the pitfalls of the language if you learn it feature by feature instead of idiom by idiom.
The fact that the Rust developers knew C++ is why they while doom to recreate it, are not recreating it too terrible. It is basically a codification of C++2014 best practices, with syntax inverted so best practices is the shortest form, and bad practices look complex, while in modern C++ it looks the opposite.
The fact you don't know C++ is why you don't like Rust syntax, and probably will not be able to understand the semantics either.
There is nothing saying you have to use every bit of it.
Other than the guy you inherited the codebase from.
Nah, he was only using the parts he knew, or thought he knew.
Unless you are inheriting it from Google, then they USE EVERYTHING for no good reason, except exceptions, but they are the exceptions after all.
Those numbers are how many have "bought" the game. So life-time total of downloads. Not all of them might have even launched it, or launched it the last 10 years.
You must have a worse memory than me, I can't stand watching most movies again, unless they are really good, and it has been a long time.
5 = almost perfect / one of the best movies of all time / give me more like this / would not watch again
4 = liked / would recommend / give me more like this / would not watch again
3 = passed the time / don't care/ would not watch again
2 = disliked / give me less like this / would not watch again
1 = hated / never give me crap like this / would not watch again
That isn't a new requirement -- a Tesla spokeswoman told Ars that the company has long asked customers to pay a $2,500 deposit when they order other Tesla models.
Model 3 buyers have always (*) been required to pay a $2,500 deposit when ordering. "other" isn't appropriate here. Is that a mistake by the Tesla spokesperson or by Ars?
It is basically how all smartphones already operate. The microphone is on all the time, an when detecting key audio signature they start sending all it picks up to Apple or Google. Those signatures being "Ok Google" or "Siri".
The last PC I had that wasn't capable of SSE2 was an Athlon T-Bird, which had a quite beefy for its time 768MB of RAM. I wouldn't want to even try running Windows 7 on that.
I had a dual Athlon 1800MP for years with 2GB of RAM, it survived surprisingly long by being dual processor, and having the GPU upgraded 3 times. It mostly died 7 years ago because everything compiled with a microsoft compiler depended on SSE2, so practical support ended 7 years.
Less than that. I had a computer without SSE2 until 2011, and by the end nothing worked. The MSVC compiler automatically enabled SSE2 and used it, which meant that all Windows application compiled after 2009 depended on SSE2. So support has been dead for at least 7 years already
The DDR memory carter is trying to yet again shift our attention from their price fixing scandals. They have been found out and punished time and time again yet it is still a profitable business practice from them. What are fines in $millions when the benefit of the price fixing is in $billions...
Yeah, the Chinese might have an ulterior motive, but what they are claiming is 100% true and a matter of simple fact. They are price fixing memory.
Slashdot Mirror
Because the RSB is shared among hardware threads that execute on the same virtual processor, this pollution enables inter-process, and even inter-VM, pollution of the RSB.
Well I guess there is a reason OpenBSD folks did this:
https://arstechnica.com/civis/...
If it requires hyperthreading, how are ARM chips affected, and I assume in this case then only the Ryzen chips from AMD would be affected, since older AMD chips had no hyperthreading?
I can only assume that Cisco has moved on from selling to the engineering teams to selling to the c-suite. That's the only explanation I can come up with for a company with multiple back-doors found in their products still being able to make sales.
Cisco has always made buggy crap. The only reason they have been working at all is because they have been industry standard so all the little players had to work around Cisco's bugs.
If your operating system was programmed well, the IO call writing to the USB drive would not return until all write buffers were flushed, would not permit large write buffers to a USB drive -and- nothing else would attempt to write the USB drive in the background.
Your operating system was not programmed well. Quick Removal only gets close.
That is bloody stupid. That is how you get 1980s IBM PC floppy performance.
To get any kind of halfway decent performance you need asynchronous IO, otherwise you can't read one place while writing another, and while updating the UI.
Was the Amiga able to sense a floppy is in the drive? PC floppies can't - the floppy controller doesn't even know if the drive is present or not, so if you disconnected your floppy drive (or the BIOS wrongly said there's one) you got a ghost drive in Windows.
If only modern operating systems had such technology.
They seem decent at warning that writes are ongoing on USB media
Yes, it could even tell which floppy you put in. Each individual floppy got a separate drive name, so it could ask for data on specific floppies, and have it automatically work if you installed extra drives and put some floppies there (you could even upload a floppy to memory, and games would use it automatically).
The third-world of the first-world. The USA has seen better days, and most of us know it.
That is what happens when your country is run by banana republicans.
They already build two laptops — three if you count the Air. They already have a pro and non-pro laptop line. The problem is that they have no clue what pro users want. If that were not the case, they would have acknowledged the feedback from 90% of users that the touchbar is a false-triggering nightmare of epidemic proportions, and they would offer an optional normal keyboard.
The have a clue, all right.
THEY... JUST... DON'T... CARE
I too had stability issues with the K6... It turned out it was related to the VIA chipset, and more specifically the drivers.. Not that they were buggy, no no, they failed to handle buggy 3Dfx, buggy NVidia and buggy Soundblaster hardware that were all violating the PCI standard, and when you had two of them (which most gamers had), there were small but non-zero chance they would step on eachothers toes due to their abuse of the PCI standard and fuck the system state up.
The non-VIA drivers and Intel BIOS all had work-arounds to keep those buggy hardware in check. After the issue was fixed in a VIA-driver update, there were no more crashes.
But as often is the case. The blame lied nowhere close to whom most people blamed.
The purchased company always pays for the acquisition nowadays, and the sooner the better.
A common strategy is to have the company you just purchased take out a bunch of debt in order to pay you back for the honor of being owned by you. They are then responsible for paying the debt back, while you walk off to the bank with your profit up front.
Depends on the level. A more typical one is to issue more shares and pay with those shares, and at the same time make one-tme bonuses to the now redundant CxOs who negotiated the buyout or merger.
Since the top management are typically not the major share holders unless they are founders, this is the best way for them to ehm.. acquire a bigger share or companies or just huge piles of cash. The whole thing is inexact enough in valution that you can extracts billions that way.
well no - that pays for the acquisition cost - what's needed now is new revenue...
You never need to pay for acquisition. Unless you destroy the companies you buy, they pay for themselves in that it makes your company's net worth increase by what you paid.
The only point you would need to pay for it, is if you mess it up, and end up writing it off, but that is pretty rare.
Facts please.
I have a 32GB Android phone and Google apps consume less than 500MB of space (including updates which still leave built-in apk files intact - that's the only way to provide safe and secure factory reset and revert to the original apps if their new versions misbehave).
Must be a magic phone. I have 16GB phone and the mandatory google apps take up 10+GB or space.
C++ is so big/complex/rich that different people or groups use different subsets, from 'better ANSI C' to 'Object hierarchies everywhere with lots of templates.' I've seen code that obviously started as "my first OO project" with classes including copy constructors and getters/setters for the most primitive structures that were later changed with basic C code and friend declarations so that this code could work around the class structure. And a bit of STL here and Boost there.
I only know three common subsets:
- Industry standard - No exceptions or RTTI, used by Apple, Google, Qt, KDE, and Microsoft. Is currently limited at C++11 or C++14 depending on project.
- Kernel safe: Mostly C with some nice syntax things and a few templates, used by GCC and various low level libraries and hobby kernels.
- Language wanking - Uses everything, used by the STL, Boost, and newbies.
The word you want is "idioms".
Every language has a set of idioms that works and C++ is no exception.
There are just more of them in C++ and the language is designed to be able to handle new ones with ease. Still newbies shouldn't be doing that, which is one of the pitfalls of the language if you learn it feature by feature instead of idiom by idiom.
The fact that the Rust developers knew C++ is why they while doom to recreate it, are not recreating it too terrible. It is basically a codification of C++2014 best practices, with syntax inverted so best practices is the shortest form, and bad practices look complex, while in modern C++ it looks the opposite. The fact you don't know C++ is why you don't like Rust syntax, and probably will not be able to understand the semantics either.
There is nothing saying you have to use every bit of it.
Other than the guy you inherited the codebase from.
Nah, he was only using the parts he knew, or thought he knew. Unless you are inheriting it from Google, then they USE EVERYTHING for no good reason, except exceptions, but they are the exceptions after all.
Those numbers are how many have "bought" the game. So life-time total of downloads. Not all of them might have even launched it, or launched it the last 10 years.
5 = almost perfect / one of the best movies of all time / give me more like this / would not watch again
4 = liked / would recommend / give me more like this / would not watch again
3 = passed the time / don't care/ would not watch again
2 = disliked / give me less like this / would not watch again
1 = hated / never give me crap like this / would not watch again
Model 3 buyers have always (*) been required to pay a $2,500 deposit when ordering. "other" isn't appropriate here. Is that a mistake by the Tesla spokesperson or by Ars?
You assume those are two different people...
It is basically how all smartphones already operate. The microphone is on all the time, an when detecting key audio signature they start sending all it picks up to Apple or Google. Those signatures being "Ok Google" or "Siri".
EULAs are "nullified" in that they are not legally binding almost anywhere.
It's okay, I only eat vegetarian ticks.
I honestly thought meat allergy was a slur for vegetarians. At least that is how I have used it ;)
The last PC I had that wasn't capable of SSE2 was an Athlon T-Bird, which had a quite beefy for its time 768MB of RAM. I wouldn't want to even try running Windows 7 on that.
I had a dual Athlon 1800MP for years with 2GB of RAM, it survived surprisingly long by being dual processor, and having the GPU upgraded 3 times. It mostly died 7 years ago because everything compiled with a microsoft compiler depended on SSE2, so practical support ended 7 years.
Less than that. I had a computer without SSE2 until 2011, and by the end nothing worked. The MSVC compiler automatically enabled SSE2 and used it, which meant that all Windows application compiled after 2009 depended on SSE2. So support has been dead for at least 7 years already
The DDR memory carter is trying to yet again shift our attention from their price fixing scandals. They have been found out and punished time and time again yet it is still a profitable business practice from them. What are fines in $millions when the benefit of the price fixing is in $billions...
Yeah, the Chinese might have an ulterior motive, but what they are claiming is 100% true and a matter of simple fact. They are price fixing memory.
iPhones are crippled
Fixed that for you.
With a nuke. From orbit.
It is the only way to be sure.