From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Oleg Nesterov" <oleg@tv-sign.ru>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
lkml <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Bart Van Assche" <bart.vanassche@gmail.com>,
"Roland McGrath" <roland@redhat.com>
Subject: Re: [patch] make siginfo_t si_utime + si_sstime report times in USER_HZ, not HZ
Date: Fri, 27 Jun 2008 10:06:56 +0200 [thread overview]
Message-ID: <cfd18e0f0806270106s5088327dja804c973bee117d@mail.gmail.com> (raw)
In-Reply-To: <cfd18e0f0806260809n4370c6eqc07c05ff93029658@mail.gmail.com>
On Thu, Jun 26, 2008 at 5:09 PM, Michael Kerrisk
<mtk.manpages@googlemail.com> wrote:
> On Wed, Jun 25, 2008 at 5:38 PM, Oleg Nesterov <oleg@tv-sign.ru> wrote:
>> On 06/25, Michael Kerrisk wrote:
>>>
>>> --- /home/mtk/ARCHIVE/KERNEL/linux-2.6.26-rc7/kernel/signal.c.orig 2008-06-24
>>> 16:20:39.000000000 +0200
>>> +++ /home/mtk/ARCHIVE/KERNEL/linux-2.6.26-rc7/kernel/signal.c 2008-06-24
>>> 16:22:17.000000000 +0200
>>> @@ -1379,10 +1379,9 @@
>>>
>>> info.si_uid = tsk->uid;
>>>
>>> - /* FIXME: find out whether or not this is supposed to be c*time. */
>>> - info.si_utime = cputime_to_jiffies(cputime_add(tsk->utime,
>>> + info.si_utime = cputime_to_clock_t(cputime_add(tsk->utime,
>>> tsk->signal->utime));
>>> - info.si_stime = cputime_to_jiffies(cputime_add(tsk->stime,
>>> + info.si_stime = cputime_to_clock_t(cputime_add(tsk->stime,
>>> tsk->signal->stime));
>>>
>>> info.si_status = tsk->exit_code & 0x7f;
>>> @@ -1450,9 +1449,8 @@
>>>
>>> info.si_uid = tsk->uid;
>>>
>>> - /* FIXME: find out whether or not this is supposed to be c*time. */
>>> - info.si_utime = cputime_to_jiffies(tsk->utime);
>>> - info.si_stime = cputime_to_jiffies(tsk->stime);
>>> + info.si_utime = cputime_to_clock_t(tsk->utime);
>>> + info.si_stime = cputime_to_clock_t(tsk->stime);
>>>
>>> info.si_code = why;
>>> switch (why) {
>>
>> This looks like the obviously good fix to me.
>
> Tested now, and it does what I expect.
>
>> The patch also deletes the comment about signal_struct->cXtime,
>> this also looks right: why should we use cutime/cstime ?
>
> Hmmm -- maybe I was wrong to delete that comment. I think the point
> of the comment was: should the time returned vie these fields of the
> signinfo structure also include the times for (grand)children of the
> process that had terminated and been wait()ed for. My first take on
> that was "no". But now I'm not 100% sure. A quick test on Solaris 8
> suggests that these fields *do* include the times of waited for
> children. (None of this is specified in POSIX.1, which doesn't
> specify si_utime and si_stime.) I've not yet tested FreeBSD (not sure
> if it supports these fields or not).
So, FreeBSD doesn't implement these fields. A more extensive test
(see below) on Solaris (8) shows that it does indeed include the times
of waited-for children in the si_utime and si_stime fields.
I'm not sure if we should emulate that behavior or not - it'd be easy
enough to do so of course. Thoughts, anyone?
Cheers,
Michael
Test
====
(If anyone has access to Tru64 or Irix, I'd be interested to see
results from the test program below.)
Using the test program below allows us to see the difference if the
child doesn't wait on it's child versus if it does wait.
# Child creates (grand)child that burns 1 second of CPU
# Child burns 2 seconds of CPU, and waits for 4 seconds
# Child does not wait on (grand)child
$ ./a.out 2 4 1
Child 17838 about to burn 1 secs
Child 17838 done
Finished burn
Finished sleep
waited for 0 children
SIGCHLD si_status=0x0; si_utime=37 si_stime=164
# Child creates (grand)child that burns 1 second of CPU
# Child burns 2 seconds of CPU, and waits for 4 seconds
# Child waits on (grand)child
$ ./a.out 2 4 1w
Child 17841 about to burn 1 secs
Child 17841 done
Finished burn
Finished sleep
About to wait for child 3 (1w), PID 17841
waited for 1 children
SIGCHLD si_status=0x0; si_utime=59 si_stime=243
==================
/* sigchld_siginfo_time_test.c
Copyright 2008, Linux Foundation
Author: Michael Kerrisk <mtk.manpages@gmail.com>
Licensed under GPLv2 or later
*/
#include <signal.h>
#include <sys/wait.h>
#include <sys/time.h>
#include <sys/resource.h>
#include <sys/types.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <string.h>
#include <errno.h>
#define errExit(msg) do { perror(msg); exit(EXIT_FAILURE); \
} while (0)
#define usageErr(msg, progName) \
do { fprintf(stderr, "Usage: "); \
fprintf(stderr, msg, progName); \
exit(EXIT_FAILURE); } while (0)
static void
handler(int sig, siginfo_t *siginfo, void *arg)
{
printf("SIGCHLD si_status=0x%x; ",
(unsigned int) siginfo->si_status);
printf("si_utime=%ld si_stime=%ld\n",
siginfo->si_utime, siginfo->si_stime);
} /* handler */
static void
burn(int nsecs)
{
struct rusage start, curr;
float t;
if (getrusage(RUSAGE_SELF, &start) == -1) errExit("getrusage");
for (;;) {
if (getrusage(RUSAGE_SELF, &curr) == -1)
errExit("getrusage");
t = (curr.ru_utime.tv_sec - start.ru_utime.tv_sec) * 1000000 +
(curr.ru_utime.tv_usec - start.ru_utime.tv_usec) +
(curr.ru_stime.tv_sec - start.ru_stime.tv_sec) * 1000000 +
(curr.ru_stime.tv_usec - start.ru_stime.tv_usec);
if (t > nsecs * 1000000)
break;
}
} /* burn */
static void
doChild(int argc, char *argv[])
{
int cn, waited, rtime;
pid_t *childList;
char *ep;
if (signal(SIGCHLD, SIG_DFL) == SIG_ERR) errExit("signal");
childList = calloc(argc, sizeof(pid_t));
if (childList == NULL)
errExit("calloc");
for (cn = 3; cn < argc; cn++) {
rtime = strtol(argv[cn], &ep, 0);
childList[cn] = fork();
if (childList[cn] == -1)
errExit("fork");
if (childList[cn] == 0) {
printf("Child %ld about to burn %d secs\n",
(long) getpid(), rtime);
burn(rtime);
printf("Child %ld done\n", (long) getpid());
exit(EXIT_SUCCESS);
} else {
if (*ep == '\0')
childList[cn] = -childList[cn]; /* Don't waitpid() */
}
}
/* Burn some CPU time ourselves */
burn(atoi(argv[1]));
printf("Finished burn\n");
/* Optionally sleep for a while, so as to allow children that we
don't wait for to terminate */
sleep(atoi(argv[2]));
printf("Finished sleep\n");
/* Wait for children */
waited = 0;
for (cn = 3; cn < argc; cn++) {
if (childList[cn] > 0) {
printf("About to wait for child %d (%s), PID %ld\n",
cn, argv[cn], (long) childList[cn]);
if (waitpid(childList[cn], NULL, 0) == -1) errExit("waitpid");
waited++;
}
}
printf("waited for %d children\n", waited);
} /* doChild */
int
main(int argc, char *argv[])
{
struct sigaction sa;
pid_t childPid;
if (argc < 4 || strcmp(argv[1], "--help") == 0)
usageErr("%s <child-run-time> <child-sleep-time> "
"<nsecs>[w]...\n", argv[0]);
sa.sa_flags = SA_SIGINFO;
sa.sa_sigaction = handler;
sigemptyset(&sa.sa_mask);
if (sigaction(SIGCHLD, &sa, NULL) == -1) errExit("sigaction");
childPid = fork();
if (childPid == -1)
errExit("fork");
if (childPid == 0) {
doChild(argc, argv);
exit(EXIT_SUCCESS);
}
pause(); /* Wait for SIGCHLD */
exit(EXIT_SUCCESS);
} /* main */
next prev parent reply other threads:[~2008-06-27 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 14:49 Michael Kerrisk
2008-06-25 15:38 ` Oleg Nesterov
2008-06-25 20:26 ` Roland McGrath
2008-06-26 15:09 ` Michael Kerrisk
2008-06-27 8:06 ` Michael Kerrisk [this message]
2008-06-27 16:33 ` Oleg Nesterov
2008-06-27 20:27 ` Roland McGrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cfd18e0f0806270106s5088327dja804c973bee117d@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=bart.vanassche@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®