From: "Rajiv Majumdar" <rmajumda@tcg-software.com>
To: Guennadi Liakhovetski <g.liakhovetski@ragingbull.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: system call for process information?
Date: Tue, 13 Mar 2001 17:47:33 +0530 [thread overview]
Message-ID: <65256A0E.004386D6.00@gemini.tcg-software.com> (raw)
every process under Linux is assigned a *task_struct* structure which has
all the info about that process eg. scheduling, accounting, I/O and others.
rajiv
Guennadi Liakhovetski <g.liakhovetski@ragingbull.com> on 03/12/2001
10:38:46 PM
To: linux-kernel@vger.kernel.org
cc: (bcc: Rajiv Majumdar/CAL/NOTES)
Subject: system call for process information?
Hello
I asked this question on kernel-newbies - no reply, hope to be luckier
here:-)
I need to collect some info on processes. One way is to read /proc
tree. But isn't there a system call (ioctl) for this? And what are those
task[], task_struct, etc. about?
Thanks
Guennadi
___
Dr. Guennadi V. Liakhovetski
Department of Applied Mathematics
University of Sheffield, U.K.
email: G.Liakhovetski@sheffield.ac.uk
-
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/
IRC Channel: irc.openprojects.net / #kernelnewbies
Web Page: http://www.surriel.com/kernelnewbies.shtml
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-03-13 12:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-13 12:17 Rajiv Majumdar [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-12 17:08 system call for process information? Guennadi Liakhovetski
2001-03-12 18:27 ` Alexander Viro
2001-03-12 21:21 ` Guennadi Liakhovetski
2001-03-13 2:56 ` Nathan Paul Simons
2001-03-13 3:20 ` Alexander Viro
2001-03-13 9:55 ` Guennadi Liakhovetski
2001-03-13 21:05 ` Albert D. Cahalan
2001-03-13 22:02 ` Nathan Paul Simons
2001-03-13 22:50 ` Albert D. Cahalan
2001-03-13 22:52 ` Rik van Riel
2001-03-14 1:53 ` Martin Dalecki
2001-03-14 2:28 ` Rik van Riel
2001-03-14 8:24 ` george anzinger
2001-03-14 19:19 ` Rik van Riel
2001-03-14 16:27 ` george anzinger
2001-03-14 1:59 ` john slee
2001-03-14 19:53 ` Szabolcs Szakacsits
2001-03-14 19:55 ` Alexander Viro
2001-03-14 20:23 ` Szabolcs Szakacsits
2001-03-14 20:21 ` Alexander Viro
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=65256A0E.004386D6.00@gemini.tcg-software.com \
--to=rmajumda@tcg-software.com \
--cc=g.liakhovetski@ragingbull.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;
as well as URLs for NNTP newsgroup(s).