From: Helge Hafting <helgehaf@idb.hist.no>
To: Gregory Maxwell <greg@linuxpower.cx>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Process vs. Threads
Date: Wed, 07 Mar 2001 10:01:21 +0100 [thread overview]
Message-ID: <3AA5F8E1.AC570516@idb.hist.no> (raw)
In-Reply-To: <20010306172843.D1283@hpspss3g.spain.hp.com> <20010306115822.A2244@xi.linuxpower.cx>
Gregory Maxwell wrote:
>
> There are no threads in Linux.
> All tasks are processes.
> Processes can share any or none of a vast set of resources.
>
Is there a way a user program can find out what resources
are shared among which processes?
That would allow enhancing ps, top, etc to
report memory usage correctly.
Helge Hafting
next prev parent reply other threads:[~2001-03-07 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-06 16:28 Process vs. Threads Jorge David Ortiz Fuentes
2001-03-06 16:58 ` Gregory Maxwell
2001-03-07 9:01 ` Helge Hafting [this message]
2001-03-07 23:30 ` Albert D. Cahalan
2001-03-08 3:09 ` David Schwartz
-- 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-08 0:17 Hank Leininger
2001-03-09 9:48 ` Albert D. Cahalan
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=3AA5F8E1.AC570516@idb.hist.no \
--to=helgehaf@idb.hist.no \
--cc=greg@linuxpower.cx \
--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