On Wed, Oct 10, 2007 at 07:50:52AM -0400, Steven Rostedt wrote:
> On Tue, Oct 09, 2007 at 11:49:53AM -0700, Mike Kravetz wrote:
> > The more I try understand the IPI handling the more confused I get. :(
> > At fist I was concerned about an IPI happening in the middle of the
> > __schedule routine.
On Tue, Oct 09, 2007 at 11:49:53AM -0700, Mike Kravetz wrote:
> The more I try understand the IPI handling the more confused I get. :(
> At fist I was concerned about an IPI happening in the middle of the
> __schedule routine. But, then it occurred to me that interrupts are
> disabled when in
On Tue, Oct 09, 2007 at 11:49:53AM -0700, Mike Kravetz wrote:
The more I try understand the IPI handling the more confused I get. :(
At fist I was concerned about an IPI happening in the middle of the
__schedule routine. But, then it occurred to me that interrupts are
disabled when in this
On Wed, Oct 10, 2007 at 07:50:52AM -0400, Steven Rostedt wrote:
On Tue, Oct 09, 2007 at 11:49:53AM -0700, Mike Kravetz wrote:
The more I try understand the IPI handling the more confused I get. :(
At fist I was concerned about an IPI happening in the middle of the
__schedule routine. But,
On Mon, Oct 08, 2007 at 11:04:12PM -0400, Steven Rostedt wrote:
> On Mon, Oct 08, 2007 at 11:45:23AM -0700, Mike Kravetz wrote:
> > Are these accurate statements? I'll start working on a reliable delivery
> > mechanism for RealTime scheduling. But, I just want to make sure that
> > is really
On Mon, 2007-10-08 at 23:04 -0400, Steven Rostedt wrote:
> On Mon, Oct 08, 2007 at 11:45:23AM -0700, Mike Kravetz wrote:
> > On Fri, Oct 05, 2007 at 07:15:48PM -0700, Mike Kravetz wrote:
> > > After applying the fix to try_to_wake_up() I was still seeing some large
> > > latencies for realtime
On Mon, 2007-10-08 at 23:04 -0400, Steven Rostedt wrote:
On Mon, Oct 08, 2007 at 11:45:23AM -0700, Mike Kravetz wrote:
On Fri, Oct 05, 2007 at 07:15:48PM -0700, Mike Kravetz wrote:
After applying the fix to try_to_wake_up() I was still seeing some large
latencies for realtime tasks.
On Mon, Oct 08, 2007 at 11:04:12PM -0400, Steven Rostedt wrote:
On Mon, Oct 08, 2007 at 11:45:23AM -0700, Mike Kravetz wrote:
Are these accurate statements? I'll start working on a reliable delivery
mechanism for RealTime scheduling. But, I just want to make sure that
is really necessary.
On Mon, Oct 08, 2007 at 11:45:23AM -0700, Mike Kravetz wrote:
> On Fri, Oct 05, 2007 at 07:15:48PM -0700, Mike Kravetz wrote:
> > After applying the fix to try_to_wake_up() I was still seeing some large
> > latencies for realtime tasks.
>
> I've been looking for places in the code where
On Fri, Oct 05, 2007 at 07:15:48PM -0700, Mike Kravetz wrote:
> After applying the fix to try_to_wake_up() I was still seeing some large
> latencies for realtime tasks.
I've been looking for places in the code where reschedule IPIs should
be sent in the case of 'overload' to redistribute RealTime
On Fri, Oct 05, 2007 at 07:15:48PM -0700, Mike Kravetz wrote:
After applying the fix to try_to_wake_up() I was still seeing some large
latencies for realtime tasks.
I've been looking for places in the code where reschedule IPIs should
be sent in the case of 'overload' to redistribute RealTime
On Mon, Oct 08, 2007 at 11:45:23AM -0700, Mike Kravetz wrote:
On Fri, Oct 05, 2007 at 07:15:48PM -0700, Mike Kravetz wrote:
After applying the fix to try_to_wake_up() I was still seeing some large
latencies for realtime tasks.
I've been looking for places in the code where reschedule IPIs
Hi Ingo,
After applying the fix to try_to_wake_up() I was still seeing some large
latencies for realtime tasks. Some debug code pointed out two additional
causes of these latencies. I have put fixes into my 'old' kernel and the
scheduler related latencies have gone away. I'm pretty confident
Hi Ingo,
After applying the fix to try_to_wake_up() I was still seeing some large
latencies for realtime tasks. Some debug code pointed out two additional
causes of these latencies. I have put fixes into my 'old' kernel and the
scheduler related latencies have gone away. I'm pretty confident
14 matches
Mail list logo