Even when discussing CPU caches, there are policies that can severely outperform LRU, specifically at the Last-Level Cache (LLC).
LLCs often are exposed to access streams where the temporal locality (which is the assumption that makes LRU good) has been filtered out by earlier caches.
For that reason, newer cache replacement policies such as RRIP, SHiP, and Hawkeye have significant headroom to improve upon LRU (and PseudoLRU).
WiFi Direct differs from WiFi Awareness in respect to the presence of the access point. In WiFi direct, there is no access point, and the devices connect directly to each other. With WiFi Awareness, an access point serves as a middle-man, but it is not necessary to access the Internet.
And neither of the two seems to have a defined minimum list of services like Bluetooth has via its profiles.
Seems Google is leaving it up to the app devs to come up with services, to expect a whole lot of silos to sprout, balkanizing the system.
On that note, i seem to recall Mozilla tried to build something similar into their Firefox for Android at some point. But i can't relocate it now because i can't recall what "catchy" codename they had on the project.
Couldn't that just be done directly on the netlist, though? I suppose this makes it easier to operate on the netlist, but I imagine there are netlist manipulation libraries that would also accomplish that task.
This is an interesting idea that has been explored before in VMS, an old operating system I believe competed with UNIX.
VMS had a feature called CLE (Common Language Enviornment) [1] which defined calling conventions for computing primitives (functions, registers, stacks...you get it) independent of any language. You could call bits of code from all sorts of languages like COBAL, FORTRAN, C, and some others I'm not really familiar with. Because the calling conventions were specifically designed for language interopperability in mind, VMS was implemented in several different languages. Different components were coded in whatever language best expressed them. This directly contrasts with Unix, which we all know champions C.
I'm not too familiar with Unix calling convention specifics, but as I understand, it revolves around C and its memory model. I believe this is what gives some languages difficulty "talking" with each other; if a language doesn't have a memory or execution model close to C's, it needs to translate through a FFI (Foreign Function Interface) [2] before exchanging execution routines efficiently.
I think Unix's pipes are better examples that how components could communicate. It's a pity that due to terminal limits, the best we can do about connecting components in Unix is to pipe things through.
USB-C and USB-3 aren't mutually exclusive.
One describes the shape (Type-A, Type-C) of the connector.
The other describes the speeds supported by the port (USB2, USB3, USB3.1).
You, however, were claiming, that rpi3 does run in 64-bit mode, just not with linux:
> The raspberry pi 3 runs in 32 and 64 mode. There is no >>LINUX<< 64-bit kernel for it currently...
To my knowledge, rpi3 has 64-bit CPU, but all operating systems and bootloaders available run only in 32-bit mode, no exceptions. That means that rpi3 in future theoretically can run in 64-bit mode, but certainly does not today.
You are claiming that you know >>all<< operating systems and bootloaders and that >>all<< run only in 32-bit mode - with no exceptions... a big claim about your knowledge...
So you know even all non-public bootloaders and OS-es...
My understanding was that the limited memory meant that it wouldn't be very useful, and they wanted to make sure that software for the earlier Pis would still be 100% compatible, and vice versa.
Actually, you can use it for free if you're a business making less than $100,000/year. Or something like that, I forgot the exact terms, but it's quite generous. The terms are shown when you first install and register the program.
LLCs often are exposed to access streams where the temporal locality (which is the assumption that makes LRU good) has been filtered out by earlier caches.
For that reason, newer cache replacement policies such as RRIP, SHiP, and Hawkeye have significant headroom to improve upon LRU (and PseudoLRU).