Thanks for a reasonable/thoughtful reply.
> to expect perfect alternation is not reasonable. the scheduler
> (or one of its subsidiary and/or supporting functions) decides what
> should run and what shouldn't. the linux scheduler did have problems
> in 2.2 (and still does in some places).
> I'm using 2.4.1-pre10, glibc 2.1.3.
And I'm using Linux 2.2. And the sched_yield bug exists in Linux 2.2. I
found
a huge number of posted bug reports on linux-kernel regarding this issue.
Check http://boudicca.tux.org/hypermail/linux-kernel/2000week21/0858.html
for one.
> Threa
wartz [mailto:[EMAIL PROTECTED]]
Sent: Sunday, February 04, 2001 3:09 AM
To: Mohit Aron; [EMAIL PROTECTED]
Subject: RE: system call sched_yield() doesn't work on Linux 2.2
The program you attached worked perfectly for me. You need to
'fflush(stdout);' after each 'printf
Hi,
the system call sched_yield() doesn't seem to work on Linux 2.2. Does
anyone know of a kernel patch that fixes this ?
Attached below is a small program that uses pthreads and demonstrates that
sched_yield() doesn't work. Basically, the program creates two threads that
alternatively t
> http://opensource.corel.com/cprof.html
>
> I haven't used it yet, myself.
>
I have. cprof is no good - extremely slow and generates a 100MB trace
even with a simple hello world program.
- Mohit
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
Hi,
I'm using Linux-2.2 and discovered a problem with the profiling of
a multi-threaded program (uses Linux pthreads). Basically, upon compiling
the program with '-pg' option, running it and invoking gprof on the
gmon.out file only shows the profile information corresponding to the
comp
6 matches
Mail list logo