From owner-cvs-all@FreeBSD.ORG Tue Mar 4 02:07:59 2008 Return-Path: Delivered-To: cvs-all@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61EEE1065671; Tue, 4 Mar 2008 02:07:59 +0000 (UTC) (envelope-from davidxu@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5EAD48FC1D; Tue, 4 Mar 2008 02:07:59 +0000 (UTC) (envelope-from davidxu@FreeBSD.org) Received: from apple.my.domain (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2427t49000179; Tue, 4 Mar 2008 02:07:56 GMT (envelope-from davidxu@freebsd.org) Message-ID: <47CCAF49.20903@freebsd.org> Date: Tue, 04 Mar 2008 10:09:13 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.9 (X11/20071211) MIME-Version: 1.0 To: Jeff Roberson References: <200803020741.m227fAoJ039644@repoman.freebsd.org> <47CB6FB0.9040602@freebsd.org> <20080302183513.P920@desktop> In-Reply-To: <20080302183513.P920@desktop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-src@FreeBSD.org, Jeff Roberson , src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern init_sysent.c syscalls.c systrace_args.c src/sys/sys syscall.h syscall.mk sysproto.h X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Mar 2008 02:07:59 -0000 Jeff Roberson wrote: >> One question is how I can determine the size of cpuset the kernel is >> using ? > > I wrote it to tolerate user masks that were much larger than the kernel > mask. I set the default CPU_SETSIZE in userspace to 128 and in kernel > it's MAXCPU. So in practice an application shouldn't have to redefine > CPU_SETSIZE. If your set is too small the kernel will return ERANGE > however. Unfortunately, if your set is larger than the kernel's > CPU_MAXSIZE it'll also return ERANGE. Maybe I should use different > errnos for those cases. > From my point, userland has to write some urgly code to guess what kernel code wants, it is rather frustrate.