DragonFly BSD
DragonFly commits List (threaded) for 2005-10
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: cvs commit: src/sys/kern kern_exec.c sysv_ipc.c src/sys/sys proc.h


From: Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>
Date: Sat, 8 Oct 2005 08:27:59 -0700 (PDT)

:corecode    2005/10/08 07:31:26 PDT
:
:DragonFly src repository
:
:  Modified files:
:    sys/kern             kern_exec.c sysv_ipc.c 
:    sys/sys              proc.h 
:  Log:
:  1:1 Userland threading stage 2.3/4:
:  
:  Use p_comm instead of p_thread->td_comm.
:  
:  Revision  Changes    Path
:  1.34      +1 -0      src/sys/kern/kern_exec.c
:  1.8       +2 -1      src/sys/kern/sysv_ipc.c
:  1.65      +2 -5      src/sys/sys/proc.h
:
:
:http://www.dragonflybsd.org/cvsweb/src/sys/kern/kern_exec.c.diff?r1=1.33&r2=1.34&f=u
:http://www.dragonflybsd.org/cvsweb/src/sys/kern/sysv_ipc.c.diff?r1=1.7&r2=1.8&f=u
:http://www.dragonflybsd.org/cvsweb/src/sys/sys/proc.h.diff?r1=1.64&r2=1.65&f=u

    Actually, I moved p_comm to td_comm on purpose, otherwise pure 
    kernel threads will not have a command that 'ps' can display, and
    processes would wind up having *two* comm[] arrays.

    I'd prefer we just have one comm[] array, which tends to 
    mean that it should be in the struct thread structure.

					-Matt
					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>



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