help-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Wait3 Questions


From: Farid Hajji
Subject: Re: Wait3 Questions
Date: Thu, 23 Aug 2001 00:55:45 +0200 (CEST)

> I started taking a look at the "time" package, which fails when
> autobuilding due to some configure tests related to the wait3
> library command.
> 
> Under Linux, this command blocks on a child process, then returns
> with some statistics about the child process.
[snip]

> Under Linux, I get information that includes some voluntary
> page faults, generated by the sleep() statement allowing
> the parent to give up its processing slice.
> 
> bfulgham@hopper:~$ ./wait3
> Parent...
> Child...
> Child done.
> Found: nvcsw=0.000000, pagflt=2.081255, minflt=2.166260
> bfulgham@hopper:~$
> 
> Under the Hurd, I get very different behavior -- no page
> faults are reported:
> 
> Parent...
> Child...
> Child done.
> Found: nvcsw=0.000000, pagflt=0.000000, minflt=0.000000
Same result under NetBSD-1.5.1 (x86):

farid@bsdevil:/tmp> ./wait3
Parent...
Child...
Child done.
Found: nvcsw=0.000000, pagflt=0.000000, minflt=0.000000

NetBSD's wait3() manpage claims conformance to XPG4:

STANDARDS
     The wait() and waitpid() functions conform to IEEE Std 1003.1-1990
     (``POSIX''); the wait3() function conforms to X/Open Portability Guide
     Issue 4 (``XPG4''); wait4() is an extension.  The WCOREDUMP() macro and
     the ability to restart a pending wait() call are extensions to the POSIX
     interface.

> Is this behavior expected -- i.e., does the Hurd handle
> swapping, etc., so differently that we would not expect
> any statistics from Wait3 in this case?  Or does this
> indicate a bug in the Hurd code?
Hmmm...

-Farid.

-- 
Farid Hajji -- Unix Systems and Network Admin | Phone: +49-2131-67-555
Broicherdorfstr. 83, D-41564 Kaarst, Germany  | farid.hajji@ob.kamp.net
- - - - - - - - - - - - - - - - - - - - - - - + - - - - - - - - - - - -
One OS To Rule Them All And In The Darkness Bind Them... --Bill Gates.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]