Remote
peter hessler @openbsd
@phessler@bsd.network
mastodon 3.5.19+iceage
I wear pants, so you don't have to. #OpenBSD developer. #c3noc. #BGP admin. #Baseball fan. Admin of bsd.network. 🏳️🌈 living in Berlin.de
2979 Followers
187 Following
11 Posts
Joined January 01, 2018
Pronouns:
They/Them
Black Lives:
Matter
I am not your:
supply chain
Replying to
@cynicalsecurity@bsd.network @aag@bsd.network I don't think big.LITTLE refers to the endianness of the cores, but to how fast/power-hungry they are.
How would you even handle mixing endianness of memory(!) or device access?
Replying to
@kurtm@mastodon.social @cynicalsecurity@bsd.network @aag@bsd.network gotta toss in a baby-mulching machine every so often.
as soon as I figure out that a thing is related to april fool day, I'm stop giving it any attention.
ban this day.
Replying to
@cynicalsecurity@bsd.network @aag@bsd.network i like the concept of BIG.little, but it sounds like a mess to actually implement and use.
Replying to
@cynicalsecurity@bsd.network @aag@bsd.network I certainly want my devices to use less power, but indeed it is a far less tempting prospect than what you were thinking of.
Replying to
@bhtooefr@mastodon.social @aag@bsd.network @cynicalsecurity@bsd.network network packets are big-endian, so it fits for the OP use-case.
Replying to
@bhtooefr@mastodon.social @aag@bsd.network @cynicalsecurity@bsd.network that almost sounds like a practical joke :)
Replying to
@kurtm@mastodon.social @aag@bsd.network @cynicalsecurity@bsd.network well, different sized cache lines isn't a problem as long as you flush the caches when switching cores.
and don't switch between them *too* often.