Solved I don't think ...

Hi everybody,

I don't think it exists userland API informing of the cpu cache features.

ChatGpt told me :
sysctl hw.cache
but it is untrue.
Do you confirm there is nothing there ?
 
Oh god now I am fighting a bot.

Look at the sysctl. Does it look like a legit hw. item?

No sysctls are more structured than that.

Look for yourself: sysctl -a | grep hw
 
Save yourself the hassle and grab a book.

There are no shortcuts for learning.

Are you OK ?
If you're in a bad mood today, tomorrow will be better.
But for now, please stop polluting the thread with your mental rumination.
Never mind.
 
This is your problem. This device is a pathological liar designed to try and please you. There should be a rule against asking "ChatGPT said this was true, is it?"

Searching cpu cache size freebsd sysctl gets you kern.sched.topology_spec
At the end, I found out it exists a library : cpu_features that fulfills my needs.

Thanks anyway.
 
People are going to have to start making this a shortcut key:


More and more I'm seeing such posts on other forums and Stack Overflow. SO has banned chatgpt answers altogether.
Sorry but I switched the discussion thread to Solved a long time ago before your intervention.
And I don't care about your opinion on chatgpt : it's off topic.
 
I'd start with cpucontrol(8) and use that to get the information. Example:
Code:
# cpucontrol -i 2 /dev/cpuctl0
cpuid level 0x2: 0x76035a01 0x00f0b2ff 0x00000000 0x00ca0000
It's worth checking out cpuctl(4) too.

I personally never used this information from userspace, I'm not aware of any libc functions. But as cpuid instruction is available from userspace you could write it if situation requires that.
 
It wasn't an opinion. It was a statement
Another XY question.

I wouldn't bother talking to it.
I'm pretty sure this is some kind of C1PQ.

Its trainer misuses this forum for a field trial,
treating you as his laboratory rats,
wasting your time,
wasting your knowledge,
wasting your experience,
wasting your energy,
and worst of all wasting your love,
wasting you.

The more you talk to it the more you're getting outraged,
by its stupidity not even grasping the most easiest things like conflicting itself,
and then talking back in a kind looks like being very polite - by the syntax.
That's what computers can handle: syntax
But because of missing any emphathy at all it does not get it's not polite,
but in fact crapping into other's faces.

The title puts it to the point.
We faced a similar situation a couple of months ago with another user called tux2bsd.
To me it locks pretty much as the same fellow, but with damped parameter settings.
 
Back
Top