From owner-freebsd-current@FreeBSD.ORG Mon Apr 23 15:58:34 2007 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DD40816A40B for ; Mon, 23 Apr 2007 15:58:34 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 9027E13C46C for ; Mon, 23 Apr 2007 15:58:34 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from [10.0.0.222] (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id l3NFZjH7077264; Mon, 23 Apr 2007 08:35:45 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <462CD251.9060105@freebsd.org> Date: Mon, 23 Apr 2007 08:35:45 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060422 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jesper B. Rosenkilde" References: <20070423113400.GC28587@gw.humppa.dk> In-Reply-To: <20070423113400.GC28587@gw.humppa.dk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Suggestions on Avoiding syscall Overhead X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Apr 2007 15:58:35 -0000 >>We can have 3 type of pages mapped into one process's address map. >>1. System wide global readonly page which will help on these syscalls: >> gethostname,getdomainname,uname >> help on importing sysenter as syscall entry point!! >> >>2. Per process Readonly page. (change will still through standard syscall) >> help on the syscalls: >> getuid, geteuid, getpid,getgid, getegid, getpgrp, >> >>3. As you planed, Read+Write Page I don't really understand this suggestion. Do any real programs call these syscalls very often? If not, this is unnecessary complexity. Making a syscall fast that's only called once doesn't really help performance. This type of approach is sometimes suggested for systime(), which could have a big impact, as there are real programs that call systime() thousands of times per second. But I find it hard to believe there are programs that call getuid() that often. Tim Kientzle