There are more than a few ways to Denial of Service other threads and or cores on most personal computers today.
Of which the most common way encountered is to probably use up too much memory causing the system to swap to the hard drive. This is partly a feature not a bug. You wouldn't like a system for personal use that would never let you do: kill -s STOP $PID So it is inherent to the design of multiprocessor personal computers that a sufficiently privileged program can bog down other cores with a bunch of interrupts, or you know power off the machine. Unless you are designing for very specialised systems such as medical equipment you don't really need to worry about it and you don't need to buy special processors or configure them in special modes to get the most determinism out of them and ensure they really are wait-free. What really matters for your purposes is that cooperating threads are wait free in practise. If you're worried that there will be some hardware bug letting people bypass cloud virtualisation and read your secured data well then I would be too. But I would be much less worried about a DOS attack against cloud services like AWS because existing distributed systems are already explicitly designed for fail over in case there is some kind of hardware failure. -- You received this message because you are subscribed to the Google Groups "mechanical-sympathy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
