People have been tinkering with L1 cache conditionality since the L1i and L1d split in 1976 but the Qualcomm people are going hard on this and the jury seems out how it’s going to play.
The line between the L1 and the register file has been getting blurrier every year for over a decade and I increasingly have a heuristic around paying the most attention to L2 behavior until the profiles are in but I’m admittedly engaging in alchemy.
Can any serious chip people as opposed to an enthusiastic novice like myself weigh in on how the thinking is shaping up WRT this?
In the GPUs I work on, there’s not really a blurred line between the actual L1 and the register file. There’s not even just one register file. Sometimes you also get an L3!
These kinds of implementation specific details are where GPUs find a lot of their PPA today, but they’re (arguably sadly) usually quite opaque to the programmer or enthusiastic architecture analyst.
It’s one thing to mirror the repos, but it’s another to initially misrepresent the interactivity the repo is getting, even if they’re clear about it when you dig in.
Also, how do you authenticate so you can keep committing and interact with the repo to manage PRs and issues if it’s yours?
The Rabbit R1 is doomed to be obsolete as soon as Google and Apple add similar functionality to their OS.
I'd much rather have something I can always manage via a local web UI from any web browser, without any cloud subscription.
Like what world do you live in that people don't complain about their old jobs such that you think it's that unacceptable?
This context does slightly soften my view, especially the part about multiple 1Password accounts being in play. However there is a big thing still missing to me... Why would Arko not immediately notify RC that he had changed the password due to these concerns?
If it was really a noble good faith action by the assigned on-call, giving a heads up to the remaining stakeholders would be the obligatory next step, no?
According to RC's timeline, the password reset happened on September 19, but Arko did not disclose the issue to RC until September 30. From what I can tell, he has not refuted that timeline or explained the gap.
They still don’t seem to be in complete control or understanding of the infrastructure they forcefully took control of.