cvs commit: src/bin/ps ps.c src/sys/kern init_main.c kern_acct.c kern_fork.c src/sys/netproto/smb smb_subr.c src/sys/sys proc.h resourcevar.h thread.h src/sys/vfs/procfs procfs_status.c src/sys/vm vm_glue.c

[Hiten Pandya <hmp@xxxxxxxxxxxxxxxxxxxxxxx>]

hmp         2004/06/20 15:29:11 PDT

DragonFly src repository

  Modified files:
    bin/ps               ps.c 
    sys/kern             init_main.c kern_acct.c kern_fork.c 
    sys/netproto/smb     smb_subr.c 
    sys/sys              proc.h resourcevar.h thread.h 
    sys/vfs/procfs       procfs_status.c 
    sys/vm               vm_glue.c 
  Log:
  Move the 'p_start' field from struct pstats (Process Statistics) into the
  thread structure and call it 'td_start'.  The behavior of vm_fork(9) is
  retained, i.e., it still copies the start time from the parent process just
  as it did before.
  
  The 'td_start' will later be used by pure threads to indicate their start
  time.  It has not been committed in this round because use of the microtime()
  function at such a early point in the boot process might be unsafe.
  
  Note, there should be no problem in accessing the td_start field, unless
  the process is a Zombie; due to the way Zombies are reaped, the thread will
  be decoupled in kern_wait1() but the process will still be around for a
  while it will not be possible to access the td_start field in such
  scenarios.  A little note about this has been added on top of struct proc
  in <sys/proc.h> for future reference.
  
  This work was a collaboration of Hiten Pandya <hmp@xxxxxxxxxxxxx> and
  Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
  
  Revision  Changes    Path
  1.7       +1 -1      src/bin/ps/ps.c
  1.34      +1 -1      src/sys/kern/init_main.c
  1.11      +2 -2      src/sys/kern/kern_acct.c
  1.27      +1 -1      src/sys/kern/kern_fork.c
  1.12      +1 -1      src/sys/netproto/smb/smb_subr.c
  1.51      +4 -0      src/sys/sys/proc.h
  1.10      +0 -1      src/sys/sys/resourcevar.h
  1.55      +4 -0      src/sys/sys/thread.h
  1.7       +2 -2      src/sys/vfs/procfs/procfs_status.c
  1.24      +1 -1      src/sys/vm/vm_glue.c


http://www.dragonflybsd.org/cvsweb/src/bin/ps/ps.c.diff?r1=1.6&r2=1.7&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/kern/init_main.c.diff?r1=1.33&r2=1.34&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/kern/kern_acct.c.diff?r1=1.10&r2=1.11&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/kern/kern_fork.c.diff?r1=1.26&r2=1.27&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/netproto/smb/smb_subr.c.diff?r1=1.11&r2=1.12&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/sys/proc.h.diff?r1=1.50&r2=1.51&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/sys/resourcevar.h.diff?r1=1.9&r2=1.10&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/sys/thread.h.diff?r1=1.54&r2=1.55&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/vfs/procfs/procfs_status.c.diff?r1=1.6&r2=1.7&f=u
http://www.dragonflybsd.org/cvsweb/src/sys/vm/vm_glue.c.diff?r1=1.23&r2=1.24&f=u