From owner-freebsd-current@FreeBSD.ORG Mon Jan 14 15:47:30 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5630B16A417 for ; Mon, 14 Jan 2008 15:47:30 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: from hu-out-0506.google.com (hu-out-0506.google.com [72.14.214.236]) by mx1.freebsd.org (Postfix) with ESMTP id 2B4A213C43E for ; Mon, 14 Jan 2008 15:47:28 +0000 (UTC) (envelope-from mozolevsky@gmail.com) Received: by hu-out-0506.google.com with SMTP id 28so806927hub.8 for ; Mon, 14 Jan 2008 07:47:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=zQu8q8SXdcML4pe7WukCliEDjlNtK+izP5jX8pwkN6Y=; b=OvvlRuaTdyyw51bIDDMM/HnuaBXERy8SyXALjapgSKIbZzMZInmJs+b/8sOvDCONnz3NSXnkbvzWYfrd+98LC9C5uV6drxuaTgY2OR7Es/G/6JimDkQW+PEfDXEu1YB3ic2M/UvvTe/bHTWF1F4cIk/G9reRByUAa6wHLHkyea4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=KXlVnKoWtN2dPSBYn5MsNjk9qIxqqVcxRcKhY9kos8V9nuWTiCu4rXwPc1Nj2ZB+CEah31OGa4wy4CFDwaKnQrNZ5n5Me0Cvdw7grjTWTjd/0mVfbtmJ9CiabUYOF4aQza4kDF2IeVEo4lC6eMzEjKQsbWKCbc4khdAiugOnCpk= Received: by 10.67.115.15 with SMTP id s15mr3436517ugm.63.1200325646978; Mon, 14 Jan 2008 07:47:26 -0800 (PST) Received: by 10.66.248.11 with HTTP; Mon, 14 Jan 2008 07:47:26 -0800 (PST) Message-ID: Date: Mon, 14 Jan 2008 15:47:26 +0000 From: "Igor Mozolevsky" Sender: mozolevsky@gmail.com To: "Csaba Henk" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1200197787.67286.13.camel@shumai.marcuscom.com> <20080113182457.GN929@server.vk2pj.dyndns.org> <200801141254.20400.doconnor@gsoft.com.au> <478AE741.1000105@comcast.net> X-Google-Sender-Auth: b98cff85a0dc2988 Cc: freebsd-current@freebsd.org Subject: Re: RFC: Adding a hw.features[2] sysctl 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, 14 Jan 2008 15:47:30 -0000 On 14/01/2008, Csaba Henk wrote: > On 2008-01-14, Igor Mozolevsky wrote: > > On 14/01/2008, Nathan Lay wrote: > > > >> cat'ing /dev/cpuinfo sounds reminiscent to Linux /proc. > > > > No it doesn't - it's a perfectly fine Unix way of doing things... The > > purpose of /dev is to provide an interface to the devices on the > > machine, (query-capable-)CPU is a device... Having /proc as an > > interface to the kernel on the other hand... > > Hm, I just fail to see the how the ioctl interface is different from > the sysctl interface in terms of semantic capabilites. You need to *define* the output of a sysctl, you don't have to produce any output in ioctl, just a boolean reply or a mask that can be processed with #define macros... I honestly don't see how all of that can be abstracted away in a MIB given that there is a number of Intel|AMD|Whoever feature/feature1, who knows when feature2 will be needed... If it can be done reasonably in a MIB, I won't say a word, but nobody's proposed any data representation for a (or a number of) MIB(s) yet... What's the overhead of sysctl vs ioctl? Igor