On Wednesday 05 March 2014 01:31 AM, David Miller wrote: > From: Allen Pais <allen.pais@xxxxxxxxxx> > Date: Wed, 19 Feb 2014 09:23:46 +0530 > >> I realized locking in tsb is very tricky. My attempts to try and get hackbench run >> without causing a stall failed. So here's what I tried to fix it, am not sure if it's >> an appropriate fix, I would love to get comments. I have tested this fix for over 24 hours >> with hackbench and dd, the system did not stall :) > > If using a local lock fixes your problem, it just means we're being > preempted during flush_tsb_user() which is absolutely not allowed. David, Its my bad, I realized my mistake of using local locks. Am still looking into the tsb flush code. It's left me sleepless. :) > The batch is a per-cpu object, and must be forcibly flushed if we > preempt. > -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
