From owner-freebsd-hackers@FreeBSD.ORG Thu Aug 11 16:15:12 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F146216A420; Thu, 11 Aug 2005 16:15:11 +0000 (GMT) (envelope-from gouders@et.bocholt.fh-gelsenkirchen.de) Received: from alice.et.bocholt.fh-gelsenkirchen.de (alice.et.bocholt.fh-gelsenkirchen.de [193.175.197.63]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09EE443D5C; Thu, 11 Aug 2005 16:15:07 +0000 (GMT) (envelope-from gouders@et.bocholt.fh-gelsenkirchen.de) Received: from musashi.et.bocholt.fh-gelsenkirchen.de (musashi.et.bocholt.fh-gelsenkirchen.de [193.175.197.95]) by alice.et.bocholt.fh-gelsenkirchen.de (8.12.9/8.12.9) with ESMTP id j7BGF4eD003045 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 11 Aug 2005 18:15:05 +0200 Received: from sora.hank.home ([10.8.0.6]) by musashi.et.bocholt.fh-gelsenkirchen.de (8.13.3/8.13.3) with ESMTP id j7BGF4XU079109; Thu, 11 Aug 2005 18:15:04 +0200 (CEST) (envelope-from hank@et.bocholt.fh-gelsenkirchen.de) Received: from localhost (localhost.hank.home [127.0.0.1]) by sora.hank.home (8.13.3/8.13.3) with ESMTP id j7BGGZWG055221; Thu, 11 Aug 2005 18:16:39 +0200 (CEST) (envelope-from hank@sora.hank.home) Message-Id: <200508111616.j7BGGZWG055221@sora.hank.home> To: John Baldwin , Sergey Uvarov In-Reply-To: Message from John Baldwin of "Thu, 11 Aug 2005 11:22:38 EDT." <200508111122.39336.jhb@FreeBSD.org> Date: Thu, 11 Aug 2005 18:16:35 +0200 From: Dirk GOUDERS X-Scanned-By: MIMEDefang 2.43 Cc: freebsd-hackers@freebsd.org Subject: Re: preferable way to control kernel module X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Aug 2005 16:15:12 -0000 > > Thank you for advise. But I wonder: what is wrong with syscall approach > > (via SYSCALL_MODULE macro)? > > I just haven't done one personally. I think there's also a lot more potenti > al > for collisions when trying to pick a syscall number versus picking a string > name for a sysctl or /dev entry. Shouldn't that be no problem if he sets the offset parameter to SYSCALL_MODULE to NO_SYSCALL (get the next free offset)? Dirk