lkml.org 
[lkml]   [2002]   [Jan]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [2.4.17/18pre] VM and swap - it's really unusable
Date
On Monday 14 January 2002 02:35 pm, Robert Love wrote:
> On Mon, 2002-01-14 at 10:02, J.A. Magallon wrote:
> > Yup. That remind me of...
> > Would there be any kernel call every driver is doing just to hide there
> > a conditional_schedule() so everyone does it even without knowledge of it
> > ? Just like Apple put the SystemTask() inside GetNextEvent()...
>
> It's not nearly that easy. If it were, we would all certainly switch to
> the preemptive kernel design, and preempt whenever and wherever we
> needed.
>
> Instead, we have to worry about reentrancy and thus can not preempt
> inside critical regions (denoted by spinlocks). So we can't have
> preempt there, and have more work to do -- thus this discussion.
>
> Robert Love

The real question is: what can get in.

Variants of the explicit scheduling points have been around for over a year,
since Ingo's original version. Just a few days ago Marcello once again said
that if all the patch does is add scheduling points, he had no intention of
integrating it. Linus's opinion on the matter has pretty much been about the
same since Ingo's version.

If explicit scheduling points ARE a better first step than preempt (which
doesn't necessarily elminate preempt, it just lets us move forward while
arguing), when the heck might they possibly appear in a mainline kernel we
don't have to manually patch each new release of?

Rob
-
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:22    [from the cache]
©2003-2011 Jasper Spaans