And someone else confirmed that they duplicate a lot of the most common units like integer ALUs so both can use it in parallel; and that each thread can use any non-duplicated functional unit not used by the other (so e.g. one could be accessing memory while the other is using the FPU)
Are you sure? I thought that was CMT (the thing Bulldozer had, where AMD got sued for misleading core count advertising) rather than SMT/hyperthreading.
Bulldozer had a seperate integer ALU for each “core” (CMT thread), but a shared FPU for each CMT cluster (pair of “cores”/CMT threads).
Although POWER8 (which has 8-way SMT) and POWER9 (which has either 4-way or 8-way SMT) apparently have varied amounts of duplicated units (and I don’t quite understand the difference between two SMT4 POWER9 cores and a single SMT8 POWER9 core, since they seem to have the same amount of slices).
TIL that in its default configuration, the Matrix Dendrite homeserver will refuse to federate over v6 entirely due to some hardcoded default ACLs that aren't documented anywhere and include "0.0.0.0/0" but not "::/0".
Very serious software.
https://github.com/element-hq/dendrite/blob/main/setup/config/config_federationapi.go#L71
@maddy @ielenia If it’s the same one as the T480s, it apparently works with open-fprintd/python-validity. I haven’t tried it though, since it’s not packaged in Alpine and I probably wouldn’t trust fingerprint unlock anyway.
@thatsten @mcc that bridge was horrible, it was frequently getting messages delayed and out-of-order (and if you weren’t careful about it, long messages and edits could be really annoying for IRC users)
also it had several security vulnerabilities discovered at various points and IIRC it didn’t handle quiets
… so whatever other IRC bouncers you’ve used must’ve been really terrible