public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hank Leininger <linux-kernel@progressive-comp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Process vs. Threads
Date: Wed, 7 Mar 2001 19:17:17 -0500	[thread overview]
Message-ID: <200103080017.TAA24960@mailer.progressive-comp.com> (raw)

On 2001-03-07, "Albert D. Cahalan" <acahalan@cs.uml.edu> wrote:

> Then for proper ps and top output, you need a reasonably efficient
> way to grab all threads as a group. This could be as simple as
> ensuring that /proc directory reads return related tasks together.
> This works too:   /proc/42/threads/98 -> ../../98

For this (but not for other "proper thread support" things you mention)
would it be enough to have /proc publish some token that represent unique
->fs, ->mm, etc pointers?  (The kernel-space address of each would work,
though that might be leaking too much info; the least userspace must treat
such values as opaque canary tokens.)  This does not give you the most
efficient "ps --threads 231" but it does let ps, top, (fuser?), etc group
processes with the same vm, files, etc, no?  ...I'm kinda surprised such a
thing doesn't already exist actually.  Unless of course, it does exist, but
is not enough :-P

--
Hank Leininger <hlein@progressive-comp.com> 
  

             reply	other threads:[~2001-03-08  0:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08  0:17 Hank Leininger [this message]
2001-03-09  9:48 ` Process vs. Threads Albert D. Cahalan
  -- strict thread matches above, loose matches on Subject: below --
2001-03-06 17:01 Dan Kegel
2001-03-06 17:32 ` Ulf Carlsson
2001-03-06 16:28 Jorge David Ortiz Fuentes
2001-03-06 16:58 ` Gregory Maxwell
2001-03-07  9:01   ` Helge Hafting
2001-03-07 23:30     ` Albert D. Cahalan
2001-03-08  3:09     ` David Schwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200103080017.TAA24960@mailer.progressive-comp.com \
    --to=linux-kernel@progressive-comp.com \
    --cc=hlein@progressive-comp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox