Date: Mon, 1 Jan 2018 06:52:37 +0000 From: David Chisnall <theraven@FreeBSD.org> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: Konstantin Belousov <kostikbel@gmail.com>, blubee blubeeme <gurenchan@gmail.com>, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: Programmatically cache line Message-ID: <08038E36-9679-4286-9083-FCEDD637ADCC@FreeBSD.org> In-Reply-To: <CAJ-VmomxGJsn8eOtWoqevdW-spUPgcSGKEc7eR4xuXLP-E1XRA@mail.gmail.com> References: <CALM2mEmWYz5nyqvxMJwMWoFOXnDTvWFrEug7UUha6xe7Um6ODw@mail.gmail.com> <20171230082812.GL1684@kib.kiev.ua> <CAJ-VmomxGJsn8eOtWoqevdW-spUPgcSGKEc7eR4xuXLP-E1XRA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1 Jan 2018, at 05:09, Adrian Chadd <adrian.chadd@gmail.com> wrote: >=20 > On 30 December 2017 at 00:28, Konstantin Belousov = <kostikbel@gmail.com> wrote: >> On Sat, Dec 30, 2017 at 07:50:19AM +0000, blubee blubeeme wrote: >>> Is there some way to programmatically get the CPU cache line sizes = on >>> FreeBSD? >>=20 >> There are, all of them are MD. >>=20 >> On x86, the CPUID instruction leaf 0x1 returns the information in >> %ebx register. >=20 > Hm, weird. Why don't we extend sysctl to include this info? It would be nice to expose this kind of information via VDSO or similar. = There are a lot of similar bits of info that people want to use for = ifunc and, SVE is going to have a bunch of similar requirements. David
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?08038E36-9679-4286-9083-FCEDD637ADCC>