[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0704061542180.6730@woody.linux-foundation.org>
Date: Fri, 6 Apr 2007 15:46:39 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Davide Libenzi <davidel@...ilserver.org>
cc: Ingo Molnar <mingo@...e.hu>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Oleg Nesterov <oleg@...sign.ru>, Robin Holt <holt@....com>,
Chris Snook <csnook@...hat.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jack Steiner <steiner@...ricas.sgi.com>
Subject: Re: init's children list is long and slows reaping children.
On Fri, 6 Apr 2007, Davide Libenzi wrote:
> On Fri, 6 Apr 2007, Linus Torvalds wrote:
> >
> > I don't really see the point. It's not even *true*. A "process" includes
> > more than the shared signal-handling - it would include files and fs etc
> > too.
> >
> > So it's actually *more* correct to call it the shared signal state than it
> > would be to call it "process" state.
>
> But "signal" has *nothing* to do with what the structure store nowadays,
> really. It's a pool of "things" that are not Linux task specific.
You're ignoring reality. It has more to do with signals than with
processes. Look at *all* the fields in the top half of the structure, up
to (and including) the "tty" field. They're *all* about signal semantics
in one form or another (whether it's directly about shared signal
behaviour, or indirectly about *sources* of signals like process control
or timers).
And renaming it really has no upsides, even *if* you had a point, which
you don't.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists