> > ehh > > why does it cause slow boots? > > if that kind of behavior changes... isn't that a sign there is a > > fundamental bug still ? > > Well it seems like the next_timer_interrupt is something like 400 > jiffies away and RCU code waits for completion for example in the > network code. that sounds like a fundamental issue that really needs to be fixed first! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Dynamic tick for 2.6.14 - what's the plan?
- From: Srivatsa Vaddagiri <[email protected]>
- Re: Dynamic tick for 2.6.14 - what's the plan?
- References:
- Dynamic tick for 2.6.14 - what's the plan?
- From: Lee Revell <[email protected]>
- Re: Dynamic tick for 2.6.14 - what's the plan?
- From: Con Kolivas <[email protected]>
- Re: Dynamic tick for 2.6.14 - what's the plan?
- From: Tony Lindgren <[email protected]>
- Re: Dynamic tick for 2.6.14 - what's the plan?
- From: Alistair John Strachan <[email protected]>
- Re: Dynamic tick for 2.6.14 - what's the plan?
- From: Tony Lindgren <[email protected]>
- Re: Dynamic tick for 2.6.14 - what's the plan?
- From: Arjan van de Ven <[email protected]>
- Re: Dynamic tick for 2.6.14 - what's the plan?
- From: Tony Lindgren <[email protected]>
- Dynamic tick for 2.6.14 - what's the plan?
- Prev by Date: Re: 8250 serial driver and PM
- Next by Date: [PATCH] custom PM support for 8250
- Previous by thread: Re: Dynamic tick for 2.6.14 - what's the plan?
- Next by thread: Re: Dynamic tick for 2.6.14 - what's the plan?
- Index(es):