A friendly tour of process memory on Linux(0xkato.xyz)
0xkato.xyz
A friendly tour of process memory on Linux
https://www.0xkato.xyz/linux-process-memory/
35 comments
I love these tiny explainers! Even if I already know what it's about, having a confirmation helps throughout reading.
"mmap, without the fog"
I don't know if this is just me being paranoid, but every time I see a phrase like this in an article I feel like it's co-written by an LLM and it makes me mad...
I don't know if this is just me being paranoid, but every time I see a phrase like this in an article I feel like it's co-written by an LLM and it makes me mad...
The article does feel like Gemini when you ask it to explain you something in layman terms, but co-authored by chatgpt with nonsense like "without the fog".
Instruction pipelining and this is exactly why I wish we still have the time to go back to "it is exactly as it is", think the 6502 or any architecture that does not pretend/map/table/proxy/ringaway anything.
That, but a hell lot of it with fast interconnect!
... one can always dream.
That, but a hell lot of it with fast interconnect!
... one can always dream.
The article is essentially describing virtual memory (with enhancements) which predates the 6502 by a decade or so.
IMO it's not even quite right in its description. The first picture that describes virtual memory shows all processes as occupying the same "logical" address space with the page table just mapping pages in the "logical" address space to physical addresses one-to-one. In reality (at least in all VM systems I know of) each process has its own independent virtual address space.
The point is that we should acknowledged those "cheats" came with their reasons and that they did improve performance etc. But, they also did come with a cost (Meltdown, Spectre anyone?) and fundamentally introduced _complexities_, which at today's level of manufacturing and end of Moore's law may not be the best tradeoffs.
I'm just expressing the general sentiment of distaste for piling stuff upon stuff and holding it with a duct-tape, without ever stepping back and looking at what we have, or at least should have, learnt and where we are today in the technological stack.
I'm just expressing the general sentiment of distaste for piling stuff upon stuff and holding it with a duct-tape, without ever stepping back and looking at what we have, or at least should have, learnt and where we are today in the technological stack.
Do you want to throw out out-of-order-execution and pipelining while you are at it, too?
I'm semi-serious: there are actually modern processor designs that put this burden on the programmer (or rather their fancy compiler / code generator) in order to keep the silicon simple. See eg https://en.wikipedia.org/wiki/Groq#Language_Processing_Unit
I'm semi-serious: there are actually modern processor designs that put this burden on the programmer (or rather their fancy compiler / code generator) in order to keep the silicon simple. See eg https://en.wikipedia.org/wiki/Groq#Language_Processing_Unit
I'm curious how this dream is superior to where we are? Yes, things are more complex. But it isn't like this complexity didn't buy us anything. Quite the contrary.
> ...buy us anything.
Totally depends on who "us" and isn't. What problem is being solved etc. In the aggregate clearly the trade off has been beneficial to the most people. If what you want to do got traded, well you can still dream.
Totally depends on who "us" and isn't. What problem is being solved etc. In the aggregate clearly the trade off has been beneficial to the most people. If what you want to do got traded, well you can still dream.
Right, but that was kind of my question? What is better about not having a lot of these things?
That is, phrasing it as a dream makes it sound like you imagine it would be better somehow. What would be better?
That is, phrasing it as a dream makes it sound like you imagine it would be better somehow. What would be better?
Think about using a modern x86-64 cpu core to run one process with no operating system. Know exactly what is in cache memory. Know exactly what deadlines you can meet and guarantee that.
It's quite a different thing to running a general purpose OS to multiplex each core with multiple processes and a hardware walked page table, TLB etc.
Obviously you know what you prefer for your laptop.
As we get more and more cores perhaps the system designs that have evolved may head back toward that simplicity somewhat? Anything above %x cpu usage gets its own isolated, un-interrupted core(s)? Uses low cost IPC? Hard to speculate with any real confidence.
It's quite a different thing to running a general purpose OS to multiplex each core with multiple processes and a hardware walked page table, TLB etc.
Obviously you know what you prefer for your laptop.
As we get more and more cores perhaps the system designs that have evolved may head back toward that simplicity somewhat? Anything above %x cpu usage gets its own isolated, un-interrupted core(s)? Uses low cost IPC? Hard to speculate with any real confidence.
I just don't know that I see it running any better for the vast majority of processes that I could imagine running on it. Was literally just transcoding some video, playing a podcast, and browsing the web. Would this be any better?
I think that is largely my qualm with the dream. The only way this really works is if we had never gone with preemptive multitasking, it seems? And that just doesn't seem like a win.
You do have me curious to know if things really do automatically pin to a cpu if it is above a threshold. I know that was talked of some, did we actually start doing that?
I think that is largely my qualm with the dream. The only way this really works is if we had never gone with preemptive multitasking, it seems? And that just doesn't seem like a win.
You do have me curious to know if things really do automatically pin to a cpu if it is above a threshold. I know that was talked of some, did we actually start doing that?
> Was literally just transcoding some video, playing a podcast, and browsing the web.
Yeah that's the perfect use case for current system design. Nobody sane wants to turn that case into an embedded system running a single process with hard deadline guarantees. Your laptop may not be ideal for controlling a couple of tonnes of steel at high speed, for example. Start thinking about how you would design for that and you'll see the point (whether you want to agree or not).
Yeah that's the perfect use case for current system design. Nobody sane wants to turn that case into an embedded system running a single process with hard deadline guarantees. Your laptop may not be ideal for controlling a couple of tonnes of steel at high speed, for example. Start thinking about how you would design for that and you'll see the point (whether you want to agree or not).
Apologies, almost missed that you had commented here.
I confess I assumed writing controllers for a couple of tonnes of steel at high speed would not use the same system design as a higher level computer would? In particular, I would not expect most embedded applications to use virtual memory? Is that no longer the case?
I confess I assumed writing controllers for a couple of tonnes of steel at high speed would not use the same system design as a higher level computer would? In particular, I would not expect most embedded applications to use virtual memory? Is that no longer the case?
"Hard Real Time" is the magic phrase to go as deep as you want to.
This isn't really answering my question. Have they started using virtual memory in hard real time applications? Just generally searching the term confirms that they are still seen as not compatible.
In addition to search engines you can learn a great deal about all sorts of things using an LLM. This works well enough if you don't want to pay. They are very patient and you canb go as deep as you want. https://duckduckgo.com/?q=DuckDuckGo+AI+Chat&ia=chat&duckai=...
Things would be simpler, more predictable and tractable.
For example, real-time guarantees (hard time constraints on how long a particular type of event will take to process) would be easier to provide.
For example, real-time guarantees (hard time constraints on how long a particular type of event will take to process) would be easier to provide.
But why do we think that? The complexity would almost certainly still exist. Would just now be up a layer. With no guarantees that you could hit the same performance characteristics that we are able to hit today.
Put another way, if that would truly be a better place, what is stopping people from building it today?
Put another way, if that would truly be a better place, what is stopping people from building it today?
Performance wouldn’t be the same, and that’s why nobody is manufacturing it. The industry prefers living with higher complexity when it yields better performance. That doesn’t mean that some people like in this thread wouldn’t prefer if things were more simple, even at the price of significantly lower performance.
> The complexity would almost certainly still exist.
That doesn’t follow. A lot of the complexity is purely to achieve the performance we have.
> The complexity would almost certainly still exist.
That doesn’t follow. A lot of the complexity is purely to achieve the performance we have.
I'm used to people arguing for simpler setups because the belief is that they could make them more performant. This was specifically the push for RISC back in the day, no?
To that end, I was assuming the idea would be that we think we could have faster systems if we didn't have this stuff. If that is not the assumption, I'm curious what the appeal is?
To that end, I was assuming the idea would be that we think we could have faster systems if we didn't have this stuff. If that is not the assumption, I'm curious what the appeal is?
That’s certainly not the assumption here. The appeal is, as I said, that the systems would be more predictable and tractable, instead of being a tarpit of complexity. It would be easier to reason about them, and about their runtime characteristics. Side-channel attacks wouldn’t be a thing, or at least not as much. Nowadays it’s rather difficult to reason about the runtime characteristics of code on modern CPUs, about what exactly will be going on behind the scenes. More often than not, you have to resort to testing how specific scenarios will behave, rather than being able to predict the general case.
I guess I don't know that I understand why you would dream of this, though? Just go out and program on some simpler systems? Retro computing makes the rounds a lot and is perfectly doable.
But why?
Website blocked as a threat/unsafe domain.
Are you on your work laptop? Your corporate IT "security theater" department may not recognize .xyz as a valid TLD.
Sounds like your security software is broken. https://www.virustotal.com/gui/url/9e0c8d513f58a8053284b8145...
False alarm.
lol
sanskarix(1)