From owner-freebsd-arch@FreeBSD.ORG Mon Jun 5 15:48:49 2006 Return-Path: X-Original-To: freebsd-arch@FreeBSD.org Delivered-To: freebsd-arch@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE5CC16A8F7; Mon, 5 Jun 2006 15:48:49 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1200A43D58; Mon, 5 Jun 2006 15:48:48 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id EAE33170DE; Mon, 5 Jun 2006 15:48:46 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.6/8.13.6) with ESMTP id k55Fmke0044259; Mon, 5 Jun 2006 17:48:46 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Suleiman Souhlal From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 05 Jun 2006 17:42:53 +0200." <448450FD.4030709@FreeBSD.org> Date: Mon, 05 Jun 2006 17:48:46 +0200 Message-ID: <44258.1149522526@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Daniel Eischen , delphij@gmail.com, MingyanGuo , Robert Watson , freebsd-arch@FreeBSD.org Subject: Re: Why use `thread' as an argument of Syscalls? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jun 2006 15:48:51 -0000 In message <448450FD.4030709@FreeBSD.org>, Suleiman Souhlal writes: >Robert Watson wrote: >> >> On Mon, 5 Jun 2006, Daniel Eischen wrote: >> >>>> They are the same questions, I think ;-). Now would you please >>>> explain "why use `proc' as an argument of Syscalls" to me :)? I've >>>> read some source code of the kernel, but no comments about it found. >>> >>> >>> I don't know. Convention? It makes sense to me. >> >> >> Certainly consistency. Most system calls do actually use the argument >> at some point -- be it to look up a file descriptor, access control, or >> the like, and the calling context has it for free and in-hand anyway. > >But couldn't they just use curthread/curproc? Yes, mostly. It's a good question how much, if anything, it helps. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.