Re: 2.6.0-test6 scheduling(?) oddness

[Murray J. Root]

On Mon, Oct 06, 2003 at 02:29:31AM +0000, bill davidsen wrote:
> In article <3F7B5584.6070604@xxxxxxxxx>,
> Ed Sweetman  <ed.sweetman@xxxxxxxxx> wrote:
> | bill davidsen wrote:
> 
> | > I wish I could just write off programs like that, but if a program is
> | > running, and doing legitimate system calls, and it stops running
> | > (totally or usefully), I'd like to be sure that the kernel doesn't have
> | > some unintended behaviour before I just pass on the program.
> | > 
> | > Particularly when OO is what allows lots of people to avoid running that
> | > other operating system.
> | 
> | it isn't doing something legitimate since as he said, it was the only 
> | program that exibited the behavior. Perhaps openoffice was exploiting a 
> | characteristic of the old schedular to increase it's performance, 
> | perhaps it's just the way they ended up coding it.  But if it's the only 
> | one then that's that.
> 
> I see nothing to indicate that any illegal system calls were made, in
> what way is it not doing something legitimate?
> 
> One program which has always worked suddenly stopping is a symptom of a
> problem, and assuming that there is no problem seems optimistic.
> Particularly when it works on BSD, Solaris, all previous Linux and even
> Windows.
> 
> If this is the sched_yeild() stuff again, I thought that was beaten into
> the ground before, and it was agreed that SUS allows it to work the way
> it has always worked and the way it works elsewhere. Hopefully this is
> not the reason performance is so grim, and a solution can be found.
> 
> BTW: I'm told that StarOffice (commercial release) also doesn't work
> usefully on test6, can anyone confirm? The test system is not overly
> stable and I don't trust negative results there.

OOo works just fine - it just won't *start* while POVRay is rendering. Once 
it's started it runs fine, even when rendering.

-- 
Murray J. Root

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