Hello, Corey. On Tue, Jul 09, 2019 at 04:46:02PM -0500, Corey Minyard wrote: > I'm also a little confused because the CPU in question shouldn't > be doing anything else if the schedule() immediately returns here, > so it's not wasting CPU that could be used on another process. Or > is it lock contention that is causing an issue on other CPUs?
Yeah, pretty pronounced too and it also keeps the CPU busy which makes the load balancer deprioritize that CPU. Busy looping is never free. > IMHO, this whole thing is stupid; if you design hardware with > stupid interfaces (byte at a time, no interrupts) you should > expect to get bad performance. But I can't control what the > hardware vendors do. This whole thing is a carefully tuned > compromise. I'm really not sure "carefully tuned" is applicable on indefinite busy looping. > So I can't really take this as-is. We can go for shorter timeouts for sure but I don't think this sort of busy looping is acceptable. Is your position that this must be a busy loop? Thanks. -- tejun _______________________________________________ Openipmi-developer mailing list Openipmi-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openipmi-developer
