From owner-freebsd-current Tue May 28 19:36:58 2002 Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (oe160.pav0.hotmail.com [64.4.33.153]) by hub.freebsd.org (Postfix) with ESMTP id B074737B406 for ; Tue, 28 May 2002 19:36:52 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 28 May 2002 19:36:52 -0700 X-Originating-IP: [210.74.136.33] From: "kai ouyang" To: "Julian Elischer" , , Subject: Re:why change: from proc to thread? Date: Wed, 29 May 2002 10:36:47 +0800 MIME-Version: 1.0 X-Mailer: MSN Explorer 7.00.0021.1900 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0001_01C206FC.BC42E0E0" Message-ID: X-OriginalArrivalTime: 29 May 2002 02:36:52.0632 (UTC) FILETIME=[B0E52980:01C206B9] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ------=_NextPart_001_0001_01C206FC.BC42E0E0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Thank you! I know a little more. From the kthread_create() function, I find Both 4.x and 5.0 are implement= ed by fork1(). I am puzzled about the structure thread and the structure proc only are d= ifferent terms. How or what part source code can I find the difference thread realization= between 4.x and 5.0? On Mon, 27 May 2002, kai ouyang wrote: > Hi,everybody > I found many v_operations, such as VOP_UNLOCK, VOP_OPEN....., there > all have a parameter(struct proc) in FreeBSD4.x, but, there all be > changed to thread in FreeBSD5.0. why? And what relation of the proc > and thread ? > Thank you! > FreeBSD is plannig on supporting threads at a kernel level. To do this, the basic scheduling element becomes the thread instead of th= e process. For this reason, for example, locks must be held by threads instead of processes, and contexts are owned by threads instead of processes. This means that most functions will need a thread pointer instead of a process pointer. The "process" becomes basically an accounting abstraction and the holder of resources, where most of the kernel is more interested in the thread. Each process has at least one thread, possibly many. Each thread is associated with exactly one process. julian=B4=D3=CD=F8=D5=BE=B5=C3=B5=BD=B8=FC=B6=E0=D0=C5=CF=A2=A1=A3MSN Exp= lorer =C3=E2=B7=D1=CF=C2=D4=D8:http://explorer.msn.com/lccn ------=_NextPart_001_0001_01C206FC.BC42E0E0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
 
<= DIV>Thank you! I know a little more.
From the kthread_create()= function, I find Both 4.x and 5.0 are implemented by fork1().
I am puzzled about the structure thread and the structure proc only are = different terms.
How or what part source code can I find the d= ifference thread realization between 4.x and 5.0?

On Mon, 27 May 2002, kai= ouyang wrote:

> Hi,everybody
>   I found many = v_operations, such as VOP_UNLOCK, VOP_OPEN....., there
> all have a= parameter(struct proc) in FreeBSD4.x, but, there all be
> changed = to thread in FreeBSD5.0. why? And what relation of the proc
> and t= hread ?
>   Thank you!
>

FreeBSD is plannig = on supporting threads at a kernel level.
To do this, the basic schedul= ing element becomes the thread instead of the
process. For this reason= , for example, locks must be held by threads
instead of processes, and= contexts are owned by threads instead of
processes. This means that m= ost functions will need a thread pointer
instead of a process pointer.= The "process" becomes basically an
accounting abstraction and the hol= der of resources, where most of the
kernel is more interested in the t= hread.

Each process has at least one thread, possibly many. Each t= hread is
associated with exactly one process.



julian


=B4=D3=CD=F8= =D5=BE=B5=C3=B5=BD=B8=FC=B6=E0=D0=C5=CF=A2=A1=A3MSN Explorer =C3=E2=B7=D1= =CF=C2=D4=D8=A3=BAhttp://explore= r.msn.com/lccn

------=_NextPart_001_0001_01C206FC.BC42E0E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message