mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karen Lenska <karenlenska@googlemail.com>
To: linux-kernel@vger.kernel.org
Cc: karenlenska@googlemail.com
Subject: Process Table-Process Control Block
Date: Sat, 7 Jan 2006 00:51:35 +0000	[thread overview]
Message-ID: <447f2a8a0601061651v63441750s98d0ef83db6f1250@mail.gmail.com> (raw)

Hi,

I wish to be personally CC'ed the answers/comments posted to the list
in response to this post



My questions are about Process ID, Process Control Block (PCB), and
Process Table (PT), and thread table



My old notes state that:

1- Each Process is allocated an identifier: Process ID (PID)

2- The PID indexes a process Table (PT)

3- Each process table entry contains a pointer to a relevant process ' PCB



However, this link

http://foldoc.org/?query=process+table&action=Search

states instead that  every process has an entry in the table. These
entries are known as process control blocks.





So I am just wondering, are the process table entries pointers to the
processes' PCB or rather the PCBs contents?



I think these entries include (among others) pointers to the PCBs
considering the latter expected size.



A second question do we use any hashing to index the process table
since the PIDs values seem not be allocated sequentially



Actually how PID values are allocated and how are they used to index
the process table (and afterwards the PCBs)



at the end, i presume that each process pcb contains a pointer to the
process thread table and that the thread table has more and less the
same structure than the process table, exempt that PCB contents is
different from Thread control block





Many thanks for your assistance

                 reply	other threads:[~2006-01-07  0:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=447f2a8a0601061651v63441750s98d0ef83db6f1250@mail.gmail.com \
    --to=karenlenska@googlemail.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

all inboxes | Powered by JetHome®