Meant by whom? To some, device they carry in their pocket is meant to be a light hacking tool. That modern devices can't do that even if the owner wants it is a travesty.
I want a game with a metagame of breeding/evolution. Cross and mutate your pets to see how they face obstacles and overcome challenges. Watch them get born and die. Watch the shape of the family tree: will it split into specialized subtrees? Will you accidentally lose some genetic diversity you need to progress?
Massive Chalice was a great example, where the pets metagame was about managing a dynasty of fighters, and at the lowest level it was a tactical fighter. The genetics system was relatively simple, and I want to see what it's like when it's developed further.
- cache entries are assumed to be looked up by the virtual address (not physical), to save a TLB lookup
- within a single page, the page line index is the same in both a physical and a virtual address
- if the cache has enough sets, it doesn't just use the line bits, but also some bits of the page address
Here's the crucial bit: a single physical page address may correspond to several different virtual addresses, so if the cache kept using virtual addresses, it might have had many copies of the same line. Kaboom.
That's why having more sets in a cache than lines in a page is troublesome.
> the attack surface it is exposed to is every USB driver in the Linux kernel, which is much worse than systems with embedded basebands and proper memory firewalling where the baseband has no more inherent access, but is exposed to a smaller attack surface.
You're saying that as if the firewall handled the communication with the modem. There's a Linux driver behind the firewall to do the actual communication, except that's probably not a USB driver.
The attack area is probably comparable, except a misconfigured USB driver doesn't automatically give full memory access, while a misconfigured IOMMU (the firewall) does.
I would be more sympathetic to the idea of the co-pilot if apart from being susceptible to stripping licensing information from permissive and copyleft projects, it could also inject copyright-stripped sources of the same amount of closed source code.
As it is now, it works towards weakening the copyright of free software while doing nothing (or very little) to closed software.
Complex structures are easier to get right in Rust than in mosy other languages, because the compiler railroads you into a subset of possible solutions that work correctly.
That being said, those structures are a subset of all possible structures and may feel roundabout. Sharing does end up being even less obvious, but it also steers you away from bugs which would be difficult to spot in other laguages. I think it comes out even here.
Does this affect anything outside the Linux kernel? Will *BSDs be able to use the specs without patent fears? What about microcontrollers, and the Arduino community?
With the given example of working with threads, I don't get the feeling that the problem is somehow fundamental to computing. It would involve the somewhat-arbitrary threading interface, with decisions differing based on the API (WinAPI? POSIX? cooperative multithreading?) someone made up, with a set of locking primitives currently in vogue (mutexes? semaphores? lockless? message passing?).
Having done a lot of systems programming, my main complaint is that I'm almost always dealing with other people's models. I might be coming across fundamental problems in algorithms, but those are a tiny part of my work.
If I remember correctly, BE helps in switching networks for routing packets. A packet would start with the big-endian destination address. If that address was hierarchical, i.e. most significant bytes signify the network (interface) it was in (like IP), then only a few of the first bits need to be processed in order to find which interface to direct the packet to. The transmission out therefore begins just after the few first bits are received.
E.g. for a switch connected to networks A: 0xa, B: 0x1, C: 0x3, a only the first byte 0x1 of the packet destined to 0x1234 needs to be processed before forwarding, saving some time compared to LE, where the entire address 0x4321 would have to be processed to find out that it's at the 0x1 network.