On Wed, 2006-05-03 at 19:25, Jan Engelhardt wrote:
> >
> >I tried to run SetiAtHome at IDLEPRIO, but it competes equally with a
> >while(1); loop run at nice 19. I'm starting to wonder if there isn't
> >some kind of bug in the kernel which results in a program returning from
> >a system call with an in-kernel semaphore held. After all, according to
> >top, SetiAtHome consumes over 90% CPU, and the system consumes only
> >about 1%, so it can't be making system calls all the time either.
>
> SAH does make very few system calls in relation to its computing, in fact.
> [It's a guess, not a proven answer.] The boinc supervisor process is mostly
> the syscall, filesystem and networking part.
>
> >This pattern just keeps on repeating, endlessly. Occasionally it also
> >has
> >
> >kill(5432, SIG_0) = 0
> >
> >attached to it. 5432 is the parent process, the FAH502-Linux.exe.
>
> You don't use boinc?
AARRGGHH. I meant FoldingAtHome.
That's what I get from not paying attention to what I'm typing ;(.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
