Matthew Dillon wrote:
: Log:
: 1:1 Userland threading stage 2.3/4:
:
: Use p_comm instead of p_thread->td_comm.
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.
Uhm, so each thread will carry the same information but proc won't?
Alright, I can back it out, it just seemed a bit weird not to have the
command in struct proc.
And worrying about these 17 bytes seemed not reasonable either.
cheers
simon
--
Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\
Work - Mac +++ space for low $$$ NOW!1 +++ Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
