Re: Process vs. Threads

2001-03-09 Thread Albert D. Cahalan
Hank Leininger writes: > On 2001-03-07, "Albert D. Cahalan" <[EMAIL PROTECTED]> 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. >> T

Re: Process vs. Threads

2001-03-07 Thread David Schwartz
> 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, to

Re: Process vs. Threads

2001-03-07 Thread Hank Leininger
On 2001-03-07, "Albert D. Cahalan" <[EMAIL PROTECTED]> 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/thr

Re: Process vs. Threads

2001-03-07 Thread Albert D. Cahalan
Helge Hafting writes: > 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 enha

Re: Process vs. Threads

2001-03-07 Thread Helge Hafting
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 m

Re: Process vs. Threads

2001-03-06 Thread Ulf Carlsson
Hi, > Can someone summarize the state of the thread changes in 2.4? > A lot seemed to happen, but from what I gather, nothing user-visible yet. We have the concept of thread group now. A thread group will be created if you use the CLONE_THREAD flag from userspace. The task structures for the

Re: Process vs. Threads

2001-03-06 Thread Gregory Maxwell
On Tue, Mar 06, 2001 at 05:28:43PM +0100, Jorge David Ortiz Fuentes wrote: [snip] > "task" that can be run. Using this structure makes easier to identify > which threads belong to the same process and tools such as ps or top > show the TID as a field. > > I understand that changing this in the

Re: Process vs. Threads

2001-03-06 Thread Dan Kegel
[EMAIL PROTECTED] wrote: > I have been trying to differenciate threads and process in Linux. As > I am sure you already know, other OS, namely HPUX, implement threads > in a different way. ... > Of course, I am talking about kernel 2.2.x, but AFAIK this has not > changed in the new kernels. It

Process vs. Threads

2001-03-06 Thread Jorge David Ortiz Fuentes
Hello everybody: I have been trying to differenciate threads and process in Linux. As I am sure you already know, other OS, namely HPUX, implement threads in a different way. There is a thread id (TID) field in the structure that is used by the scheduler and it is used to identify uniquely eac