lkml.org 
[lkml]   [2002]   [Feb]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Lse-tech] Re: [PATCH] O(1) scheduler set_cpus_allowed for non-current tasks
On Fri, 22 Feb 2002, Ingo Molnar wrote:
>
> well, how do you migrate the task from an IRQ context?

Let it remove itself, in due time.

> even if it worked, this adds a 1/(2*HZ) average latency to the migration.
> I wanted to have something that is capable of migrating tasks 'instantly'.

That's the key question, from my perspective.

I was not aware of any need for instant migration, and to
the best of my knowledge, a clock tick latency was just fine.
But if your intuition suggests its worth supporting instant
migration, go for it.

The main concern I had with Erich Focht's patches that also
attempted instant migration was that Ingo wouldn't agree.
Somehow, I don't think that concern applies for your patches.

Thanks, Ingo! I'm delighted with the outcome.

--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:24    [W:0.350 / U:0.532 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site