Date: Mon, 14 Jan 2008 01:21:15 +0000 From: "Igor Mozolevsky" <igor@hybrid-lab.co.uk> To: "Peter Jeremy" <peterjeremy@optushome.com.au> Cc: Kostik Belousov <kostikbel@gmail.com>, Joe Marcus Clarke <marcus@freebsd.org>, current <current@freebsd.org> Subject: Re: RFC: Adding a hw.features[2] sysctl Message-ID: <a2b6592c0801131721w25afae5bg3dcf6a90c1a3d2b7@mail.gmail.com> In-Reply-To: <20080113182457.GN929@server.vk2pj.dyndns.org> References: <1200197787.67286.13.camel@shumai.marcuscom.com> <20080113064450.GW57756@deviant.kiev.zoral.com.ua> <20080113182457.GN929@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13/01/2008, Peter Jeremy <peterjeremy@optushome.com.au> wrote: > IMHO, no. Virtually all similar FreeBSD information is exported via > sysctl and this sort of information fits neatly into the existing > MIB tree as either dev.cpu.N.features or hw.cpu.features /dev/sndstat? If it's in /dev you can do neat tricks like ioctl-ing queries (like ioctl(/dev/cpuinfo, CINFOCTL_HAS_FEATURES, CINFO_SSE3|CINFO_SSSE3)) instead of having *every* app parse the result of a sysctl; most of the time you'd only want to check for specific feature , it's much easier to do an ioctl that returns a boolean. Igor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a2b6592c0801131721w25afae5bg3dcf6a90c1a3d2b7>