Re: [PATCH] 2.4.9 Make thread group id visible in/proc/<pid>/status

[george anzinger <george@mvista.com>]

Dave McCracken wrote:
> 
> --On Monday, August 20, 2001 11:50:37 -0700 george anzinger
> <george@mvista.com> wrote:
> 
> > Are you possibly also looking into allocating a small data structure to
> > the thread group?  A place to keep thread group signal info, perhaps?
> 
> No, not specifically.  A mechanism already exists to share info between
> cooperating tasks, where there's a common structure pointed to by each task
> (ie mm_struct, signal_struct, files_struct, fs_struct, etc).  I think we
> can use this mechanism for any info a group of tasks needs to share.
> 
But this (signal_struct) does not share the signals, just the
infrastructure.  I believe the thread standard defines some signals that
are to be delivered to a "thread leader" regardless of what actually
caused the signal.  Thus for these signals a separate mask & signal
queue seems in order.  I suppose one could use the union of all the
thread masks or some such, but this seems like a lot of overhead.  Also
need to introduce the concept of a "thread leader" (the thread that this
group of signals is to be delivered to) and what happens when the
"thread leader" exits (how a new "thread leader" is chosen).  I suspect
that the standard addresses all this, but I don't yet have access to the
standard.

Then, again, I could be suffering from too much coffee :)

George