Why don't we make an OS from scratch with no Unix and no (minimal) legacy bloat?What would be the best architecture for this modern OS?
>>108477409cool. produce a hardware platform with publically available schematics, documentation and no obfuscation of the chips utilized by this hardware. maybe then.. sure. i'll draw the logo. but now? with today's slop and locked down hardware? christ no. waste of time. we need to start from scratch and with no interference from lawyers from israel and the united states.
>>108477424The biggest problem is the GPU, it could start off with a CPU renderer until it's figured out.
>>108477409all the system sounds must be autistic screeching.
So, who's writing the drivers?
>>108477424this
Windows2000/NT6.2
>>108477409First: Are we going to implement age verification? Very important.
>>108477409What’s the governance structure? How many seats on the leader ship council? There should also be a project lead, and it should be a diverse female.
>>108477409We would need to establish a Code of Conduct that's welcoming to all people and those who don't identify as people.
>>108477409We need a better language first.>>108477458What a retard.
>>108477866And more importantly: tabs or spaces?
>>108477466>The biggest problem is the GPUsad but true>start off with a CPU renderer until it's figured out.yes. and since we're not having to support the half century+ of unix nonsense we can write some blazing fast routines using 2026 CPU tech.
>>108478153Tabs, but anyone who fucks up spacing will be permanently banned
>>108477409single threaded only, single process only. kernels and were a mistake
It refuses to boot on any indian subnet, first thing it does is on loading an IP stack check it's public IP address and shuts down and corrupts itself if it finds it is in India or Pakistan etc. Only supports ASCII.
>>108477926based
closed source and obfuiscated before compilation only the single thread and single process can check the value in a register or it shuts down and corrupts itself. Supports raw sockets
>>108477944Of course. Need to know where cunny hides.
>>108477409Go for it. https://rentry.co/g7aofwhc
>>108478271the sigle process must load and provide the equivanent of chromium, codecs, ms paint, a clock and an IP stack and wordpad and a spreadsheet, no printers, It has a copy of doom in memory at all times and uses the reguster values in memory for doom as hashes to encrypt and decrypt all values it's writing to other registers. There is no way to run other applications unless the entire OS is recompiled
All code must be spagetti code, no exceptions and synthal is limited to the C library. Extra appreciation to code containing gotos, comments are banned
Um im literally taking os right now in college and I already figured it out. At first I thought we could just use gpu cores and wouldn't have to worry about scheduling because your computer will just turn off if it ever tries to make more threads than cores but I guess you cant do that for some reason so I invented the best method, you have many small batch cores that uses sdlf, if there would be a miss the longest work remaining thread gets sent to the singular super beefy fifo massive clock speed core. We can use fpga to get the logic down or whatever before printing real chips.
>>108478391single thread single process or go home, everything else is inrinsically insecure
>>108477409I'm making one, it's single process, ARM, no MMU and no compatibility with previous slopI plan to make a cyberdeck using it
>>108478391Oh yeah the individual cores on a gpu arent freaking addressable for some reason you can only send a batch of jobs to like a 100 for some reason.
obligatory
>>108478437Here's the link by the wayhttps://github.com/reshsix/vermillion
>>108478437If you had 128gb of ram would fragmentation even be an issue? All your programs would have to know where they want to go in memory or would it be only one program allowed in memory at once?
>>108478495Oh wait mmu just does paging you can still find the next section of memory big enough without it.
>>108478495I have a malloc that I want to simplify on future to avoid fragmentation Programs load on the next free space of the heap, which can be also occupied by "terminate and stay resident" type of programs (which I called libraries)The plan is to use more static allocation than dynamic inside them, by providing good limits to things
>>108478445Computers are either autism boxes, or data surrendering boxes
>>108478519MMU point is just to protect memory zones and scramble addresses I hate it because it doesn't let user programs interface with memory-mapped devices
Alternative idea: let's just use the Linux kernel, fork GTK2 and I will make a CSS stylesheet that makes it look more like Mac, but like, more Mac than Mac.
The guy who wrote UNIX did it on his own in a matter of weeks. Why does no one else do this anymore?
>>108479319Come to think of it, forced cooperation, force teami-ification, corporatization, what have you, is kind of the problem. If you think about great works: books, art, software, the person who initially built it was usually a lone wolf. No interference, no arguments, no debate, just a singular, cohesive vision. There can't be a cohesive vision if there are multiple people involved.So really when we talk about the "next UNIX" or the "next Windows", it really does have to be one brilliant guy lone wolfing something magical together and then it snowballing from there. Other developers come in as the project gains traction and the bones/architecture are done, providing a blueprint for the extensions.
>>108479300Yeah, dude lets ignore that most problem are inherited from C and the UNIX mindset.
>>108479319No wonder why it sucks.
>>108479351There is like 0% chance that the best possible implementation of an OS happened right as computing was in an infant state and just starting to grow. It's just that we're scared and lazy and can't pursue anything else now, it's "'good enough" and got first mover advantage.Why don't one of these infinity rich faggots like Musk hold a competition with prizes for whoever can write the best OS, figure out some kind of standard rubric in terms of performance, memory usage, reliability, and just let the mass of unemployed and underemployed autists go to town. Winner gets to spearhead his startup.
I'll make the logo
>>108478067>We need a better language first.An all-lists (Scheme/Clojure inspired) Haskell (purely functional.)>>108477458What a clever.
>>108479444>https://rentry.co/g7aofwhcOr Erlang it is fucking fast designed for Ericson !
>>108477409If you were to build an OS for the next century, it would probably collapsed the thousand layers that have bubbled up into a hypervisor and loadable modules like wasm using a WIT system
>>108478305Redox recently put capabilities into theirs. It might be the only real advancement in OS. While that article makes a lot of good points, the new semantics stuff is more prescriptive than real.
>>108479372Screenshot this and tag him in it on Xitter. He could find this with his pocket change.
>>108479319There's lots of OSdev projects like the one that was posted here, but they don't gain adoption because people want "le best thing", and to satisfy all the bogus requirements they want only windows/mac/linux can
>>108479372Because nothing is the best at birth, an OS could win the competition then be shitty long term, which is basically what happens all the time with venture capitalism fund winnersThe problem is wanting "the best", "the objective best" instead of "this one I like the most", because "the objective best" is sticking to the already tested and mature crap
first of all it should be based on superior runtime without retarded threading model.after some studies of shared memory i conclude that new OS should have APIs to share already allocated memory. now all OSes have some retarded file-to-memory mapping which is also involves retarded page file concept. so> no page file> allocated memory sharing via specialized API (no file word in there)
>>108479319>matter of weeksbecause it was written for a computer than only had 4kb of ram. are you stupid or just pretending to be retarded?
>>108479516And they are doing nothing wrong. I want a new OS for design elegance, but even an extremely well designed OS wouldn't have much better performance in any area except for very specific ones.
>>108479602They are, once you optimize for sake of optimizing, you make a square into a circle, which is meaningless and forgettableYou don't need server level performance for user software, you just need the thing to work without lagging, which can be achieved by limiting features
>>108477409Linux.
>>108478067>What a retard.Well if you insist on being non-Unix, you could look at Plan9 or BTRON for ideas I guess.
>>108477409>What would be the best architecture for this modern OS?Just copy seL4, it's a nice modern microkernel, and a fast one at that.
>>108478596Can't you just use mmap for that? Kernel driver exposes your device as a block device and you mmap to expose to your application or use block device API via ioctl, etc. directly. MMU also can virtualizing memory addresses so you can have codes all linked to same address and run them at the "same time". This also allows to share memory between codes e.g. two codes rely on same data linked at say 0x0000000008001000 then MMU puts that data there and both codes can use the same.
>>108479687Problem is having to write a kernel driver when you just want to set 0x8000 to 1You can use /dev/mem but the kernel may get in your way (need sudo, it can overwrite your memory, writing a memory address becomes writing to a file now), for embedded is a hassle
>>108477409Genera running on a Lisp machine.http://lispm.de/genera-concepts>>108478067>We need a better language first.There's Common Lisp, which could easily support languages like Python and JavaScript too. You could just share objects between languages.
>>108479701C and Unix (which includes Plan 9) are why there is no reliability and security in software anymore. Buffer overflows went from something that can't happen in high-level languages and were only created by noob assembly programmers to being enshrined in an ISO standard because of C and null-terminated strings.
>>108477409Honestly it should be like a console.Everything is read-only except one folder for dumping user files.All programs are either already part of the system or "installed" by recompiling the OS onto a new single-write memory (as in, once written it becomes read-only).Limit programs to 100 MB of data. There's no memory management except each program can be loaded or unloaded from a 100MB chunk of RAM.Single thread, one process at a time except each process must implement the Exit routine bound to a standard key like Escape which returns control to OS. Memory corruption or other issue is fixed by restarting OS. OS loads in under 2 seconds btw.Programming language? A simple wrapper over standard CPU instructions to give readable names and syntax. No "compilation", no "variables", no "scope", libraries are just code you write to memory (the whole 100MB is executable).Logo? A digitized 30x30 binary pic of Arnold Schwarzenegger giving roman the salute.Name? Something that scares normies away.
>>108477424>uhh you can't do that goyim because t's really hard o algoThey're not sending their best
The best approach to making an OS is from the outside in. You build the UI and userspace inside a hosted OS, then you defer the boring stuff (drivers, syscalls, compilers, etc.) for the end when the OS is working.Having said that, even if you make a good OS, there's the problem of having no software written for it.Never mind the fact that /g/ would be utterly incapable of writing a good UI toolkit (actually you guys wouldn't even settle on a kernel architecture, you'd spend 5 years arguing over it before writing a single loc)
>>108480376More like when projects here exist people are too busy imagining things instead of using/participating
>>108480144entertain us more, mr.Clown
>>108477466Intel has public documentation for their GPUs
>>108477409We had some discussions about this in the past /aosg/ generals.
>>108480852The Wiki is back online.https://igwiki.lyci.de/wiki//aosg/_Alternative_Operating_System_Generalhttps://igwiki.lyci.de/wiki/ShimOS
>>108478067>We need a better language first.Ha, the usual trap. I knew AI researchers in the 90s who said the same. The next 20 years they were building "better languages" instead of AI.
>>108479383Damn it, i wanted to make the logo
>>108478445>no kensington lockdisgusting
>>108477409>legacy bloatWhy not start out with modern Linux kernel and then rip out all the misbegotten APIs? Their API/ABI promise means it is accumulating cruft. Also the glibc is full of idiocy such as strfry. Rip it out.SerenityOS has no API/ABI promise and can experiment as much as they want.
>>108481504Idk what that is and I don't care (I'm employed)
>>108477409ReactOS is the way to go; Windows NT has proven itself to be a good OS in the 2000's, and there is so much existing software made for those old Windows systems.
>>108481762Before that, VAX VMS proved itself as rock solid.
>>108481967i bet this screenshot wasnt made from VAX VMS OS
>>108477409look at how CloverOS is going op
>>108477409Make it retarded simple.It is very hard to make a mistake if there's only 500 lines of code.
>>108482359and the only functionality should be the display of the logfag with /dmp/ trash playing
>>108482374That was uncalled for...
>>108477458Counterpoint:
>>108483546He never said that.
>>108483551Cutler's hateboner for UNIX is well documented. There is a reason of why Windows NT is basically the Anti-UNIX OS.
>>108483558And with good reason
>>108478251No. It degrades enough to deter them, but not enough to get them to jump ship. The sweet spot would be if it drives them to an heroing.
ponyos and kolibrios both pique my interest but their build env is dog shit
>>108484079KolibriOS is good, but it's only 32-bit and its development is quite slow.MenuetOS (KolibriOS' ancestor) actually is 64-bit and has a faster and consistent development, but the creator of the project had a tantrum years ago and closed the source code. MenuetOS was originally licensed as GPL.
>>108484079>ponyosStrange choice, why not ToaruOS instead?
>>108478051Identify is a bit ableist, yo.
>>108480369t. jewish/american lawyer that misses the point. starting form 0 with entirely new hardware is the only solution. cope, rabbi.
>>108479534these days its stupid to attack such projects (OS) head to head. new ideas dont come from nowhere so OS+runtime is optimal combo.i did example of terminal in the past, xterm + ncurses, is one of the examples how big projects developed. you have major thing and you have minor thing that is used to test it, they compliment each other.
>>108477458It should be "Those who only understand Unix are condemned to reinvent it, poorly." Like Plan 9, Linux, and BSD. Those are all Unix "reinvented poorly." They didn't fix any of the fundamental problems of Unix and just tack on more bloat and complexity on top of a bad design. People who don't care about Unix make something completely different, like Genera, VMS, and Classic Macintosh. If you want to make something better, you have to use and understand other operating systems to learn Unix isn't the only way to do things.
GNU/seL4 was the perfect FREEDOM® OS but the retards at the Free Software Foundation didn't have the balls to make it happen.
>>108477458>they hated him, because he told them the truth
why, there is plan9
>>108485296If you don't understand Unix, the OS you design won't be anything like Unix. You're not going to parse text from commands to get information (like piping ls to awk), you'll be using some kind of API that gives you a struct or object with the information you need. In Lisp, all of that would be handled with methods and functions, not pipes or text parsing at all. There would be even more fundamental differences too. It's only people who worship Unix who insist on reinventing it and copying everything about Unix.
>>108478153spacestabs are inconsistent, a single tab character is sometimes longer, sometimes shorter
>>108479534I think this anon is onto something, how hard would it be to create architecture where the program counter just keeps going and keeps allocating the next instruction to the next core? One register bank, one cache. No page table because every process executes immediately running dozens of instructions simulatenaously. The only issue is all programs would have to be able to fit in memory.
>>108485283GNUSEL FOR.. you?
>>108485246>like Genera, VMS, and Classic MacintoshThere are a lot more. The Japanese struck gold with the TRON family, but then proceeded to do nothing with it.
>>108485400i said no page file, or swap file. swap file is a feature to expand memory to filesystem. this is not needed anymore, this was prototyped in the days when memory was very limited.
>>108485798TRON was killed by Reagan because the US got scared of Japan being too based.
>>108485246>the fundamental problems of UnixSuch as?
>>108486898TRON is perhaps client terminal and big computers have other name
>>108484684literally the same but which one do anons know by ear?
>>108487005Stream file philosophy, pipes, untyped sequence of byte "files", parsing text output intended for humans as input to other programs, fork, conflating processes with address spaces, no ability to call programs in the same process, bad signal design, multiple overlapping obsolete features, no standard command argument parsing, null-terminated strings, EINTR, termcap philosophy instead of standard terminal API, etc.
>>108486898nah, Japan survived because Reagan killed TROON project.>>108487223file "streams" break unix philosophy though, one thing that does multiple jobs, instead of doing one job. null-termination is a primitive encoding which is good for low level. command line arguments AFAIK is much easier to parse than on windows, WIN version has a quirk dependency on user32.dll that brings some lag, so you have to make non-standard function to avoid it, though, these 2 are little issues. NIX has absolutely retarded module/binary linking, its less dynamic and bound to libc. this is the major problem on NIXes, theres a video of Zig's author who tried to solve it 5-6 years ago
>>108487601>file "streams" break unix philosophy though, one thing that does multiple jobs, instead of doing one job.Except that's how Unix works. Something fundamental to Unix breaks the "Unix philosophy" because Unix philosophy is a lie.>null-termination is a primitive encoding which is good for low level.It's not good for anything. If you know assembly or how computers work, you'll know it's stupid and it leads to all the buffer overflow problems and it's slower than regular strings.>command line arguments AFAIK is much easier to parse than on windowsOn Windows, you can get arguments like ren *.txt *.bak but on Unix, you can't because the shell "globs" arguments first. You can't get the real command line on Unix.
>>108487223>pipes, untyped sequence of byte "files"OK, now we are getting into the interesting details. So what are the problems with these two, and more importantly, what would be a better solution if we are not bound by any compatibility requirements?
>>108487753>that's how Unix worksthats how libc FILE works, there is the culprit, nothing to do with UNIX word.>It's not good for anythingpropose simplier encoding (you cant)>it's slower than regular stringspremature optimization nothingburger>you can get arguments like ren *.txt *.bak butwe talk about OSes here, not shells. program gets arguments with the help of libc abstraction, or, by using system APIs
>>108487753>the shell "globs" arguments firstYou can quote the arguments to escape globbing, though most programs rely on the shell for such processing.
>>108488126>So what are the problems with these two, and more importantly, what would be a better solution if we are not bound by any compatibility requirements?Passing objects directly instead of pipes. Typed persistent objects that can be accessed directly instead of sequences of bytes that are streams.
>>108486898That's a meme. Japan barely gave a fuck about the international market and always did their own thing, like the PC-98 machines.If TRON didn't flourish is because they didn't know how to manage the project and it became too expensive for them to maintain. It became too expensive that it was easier to import foreign machines and software, thing that they did.
>>108481967>VAX VMSIf DEC were not running by retards, they could have taken Microsoft's place in the industry.
>>108489474>That's a meme.No, it's both of our posts. The US didn't like it because it was Japanese donut steel. PCs probably still would have won, but Japan was pressured to stop and that allowed them to save face and do what they did.
>>108490383>they could have taken Microsoft's place in the industrydec was more at ibm and intel level for a time. i don't think they would have had any interest in taking microsoft's "place" as microsoft were mostly making lesser shit right up until the 1990s using ibm/ibm clone hardware. dec's hardware designs were aging and its management were pretty useless at foreseeing future trends. it was destined to die at any rate.
>>108489474You should really look up what happened, that and the Plaza Accord.The Japanese knew how to make projects flourish and that is what made the US panic.
>ITT losers with no talent at anything demoralize other losers with no talent at anything into doing nothing and crying about itIt's so bizarre being literally the only person on the "Technology" board that knows how to use a computer to actually create or accomplish things, instead of just playing tinker toys with a command line and thinking they're leet pro hackers.
>>108491001What are you talking about? Are you ok mentally?
>>108477409I’ve been collecting thoughts on this for a while:https://portal.mozz.us/gemini/gemini.circumlunar.space/users/adiabatic/words/computing/ideal/os/>>108478153we have gofmt nowTabs for indentation, spaces for alignment >>108488126Consider Mac OS that, well before the NeXT guys got in, had type and creator codes front and centerSo HTML files you made in BBEdit would open in BBEdit but that file you downloaded with IE5 would open in IE5Also I think BBEdit stores per-document font preferences in extended attributes But these things don’t get preserved with UNIX tooling that assume a file is a block of bytes and you need to compress stuff with zip to preserve that kind of rich information NTFS has multiple data streams per file but basically nobody uses themIt’s hard to beat a zip file with XML files in it
>>108478067>We need a better language first.Smalltalk is top tier for operating systems. You literally can modify an OS on the go with it.
a good kernel already exists in the form of sel4 and the bsd net stack is basically perfect. start writing drivers, a file system, and some user software for it if you care that much
They only real reason none did it before is because its huge and time consuming endeavor, but with support of KI it becomes more realistic no? And no i dont nean to vibe code a complete OS although funny
>>108485246I doubt he means that. Zealots praising UNIX are very common in tech circles anyway you can't do it worse even ignoring UNIX gotchas.
>>108490721>i don't think they would have had any interestAnd that was the problem. Tech was good, management not so much.
>>108477409I was thinking of an idea of reinventing "unix" with Windows like features to it. with a Linux kernel.We need a standard like Api like Win32 on Linux.The problem is I can't program and not to the extend where it makes sense to create a new user space form scratch.Unix sucks, Gnu sucks but less and the alternatives aren't better. Win32 however is a great.
>>108477424There's Risk-V. It's mostly chink tech, but it might become something Europe commits to as well. It's like ARM, but you don't need the loicense to use Risk-V standard.>>108477409> Why don't we make an OS from scratch No reason.> no Unix Some say you either have UNIX, or would have to reinvent it, poorly.> (minimal) legacy bloatNo support for obscure hardware? Good luck with your Vista-like reputation, you will go far.>>108477466There are open source drivers for AMD afaik. For nvidia as well, although they are shitty.>>108477944Age verification requirements in our new OS:1. You have to be at least 38 years old to contribute C++ code.continue this list.
>>108478221>>108478153Why would you assume /g/ would have even a single line of Python code in the codebase for this to be a relevant question?
>>108488466Which OSes do this well? I have tried Haiku but cannot really see much of the object oriented nature there.Strangely, many object oriented operating systems seem to have failed.
>>108492701I’m not the guy you’re replying to but I think PowerShell does this well>HaikuIIRC BeOS’ OOness mostly comes from how it uses C++ as its main languaget. used to write C++ but never wrote any programs for BeOS
>>108488466>Passing objects directly instead of pipes.What about agents, Magic Cap style? Objects are kind of alive (no AI) and can also make their own decisions.
>>108492644>Some say you either have UNIX, or would have to reinvent it, poorly.No, there are a lot of operating systems out there that aren't like UNIX at all. Have you ever used a Classic Mac, Oberon, Genera, Mezzano, KolibriOS, CP/M, VMS, or a non-UNIX mainframe or minicomputer OS? Windows isn't like UNIX except for being written in C, but the Win32 API and NT kernel and API are very different than UNIX.
>>108492635>We need a standard like Api like Win32 on Linux.Why not Win32 itself? There is a reason of why some devs say "Win32 is the only stable API on Linux".
>>108493795>Why not Win32 itself? There is a reason of why some devs say "Win32 is the only stable API on Linux".Because of these reasons:1. it's archaic unless you want a Windows clone this is not the way to go. The idea is good the implementation while stale works, but it just doesn't make sense copying something completely form the past when modern hardware acts different. There is lot's of stuff in Win32 that is deprecated and extensions added.2. Microsoft owns Win32 at the end of the day you are going to have to copy everything Microsoft does and not innovate on it and might get you in a lawsuit.
>>108491133>’ve been collecting thoughts on this for a whilenice, now i know what compukter display and keyboard you want (completely irrelevant to an OS)>>108491604>Smalltalk is top tieri prefer BigTalk language, others prefer SqueakTalk, other others prefer.. the list goes on, though observations show that it is C-like syntax>>108492635Linux already has "standard like API", its called syscalls and they are made with assembly. LIBC does them and it is attached to the program. Win32 is the same but it is not attached to the program rather linked. words like "great", "exciting" and "satisfiction guaranteeed!" dont mean anything.>>108493671>but the Win32 API and NT kernel and API are very different than UNIX.different not so much different >>108479534 same "streams" concept that in GNUnix btw. but i can i agree win32 is much comfier and better named.>>108494193>it's archaic unless you want a Windows clone this is not the way to goarchaic compared to Linux syscalls? to LIBC v1 v2 or what?>The idea is good the implementationthe implementation is better than the idea. the idea where to put APIs is not obvious. having an abstraction layer makes OS more expensive - more documentation to write, more code to maintain. its also a bigger set of "forever" APIs (nothing is deprecatable). also it doesnt guarantee the user wont slap a retarded LIBC or .NET on top of it. nobody seem to write WINAPI these days, this considered "system programming", while being user concern. so this is a proper critique of win32.
>>108491133>NTFS has multiple data streams per file but basically nobody uses themNTFS has shitload of functions that Windows will never use because of its outdated API.
>>108477409GG NO REhttps://www.linuxfromscratch.org/
>>108478445If that's a 10:16 CRT display, sign me up!
>>108477409Let's start a project on Radicle, it's like git but it's a peer-to-peer software and anyone can commit its shit.Could be fun.
they already made the /g/ approved OS, but nobody wants to actually use ithttps://www.youtube.com/watch?v=YwgPMNH31XI
>>108495371>SymbOSMy negro. Best retro OS in existence, hands down.
>>108495371Tragically, the 6502 equivalent project is stuck. https://www.youtube.com/watch?v=T14dL9MeMHEhttps://atari8.co.uk/gui/
>>108487223>conflating processes with address spaces, no ability to call programs in the same processWhat is the problem with these?>bad signal design,Sure. How to do it better? Could one use objects instead of signals?>multiple overlapping obsolete features,Definitely a problem with Linux, they should declare a flag day every 10 years.>no standard command argument parsing,Isbn bash a good enough standard?>null-terminated strings,Why?>EINTR,Not sure what you mean here.>termcap philosophy instead of standard terminal API, etc.is plan9 better in this respect?
>>108477409Single user, everything is Ring 0.
>>108487005"/" is degeneracy that only makes sense if you have merely one disk. Everything falls under the root directory even if it isn't on the root disk, it's retarded.
>>108496056Based DOSCHAD
>>108496089That is just abstracting, what is really the problem?
Whatever architecture supports thread-local page translations.>whyBecause microkernels only support submitting one request at a time. You want to avoid mode switches, you have to make it a monokernel that supports submitting multiple (read: hundreds or thousands) of requests at the same time. In order to avoid the nonsensical CVE clusterfuck that is io_uring we either have to write-lock the input pages, or copy the data into the kernel. Write-locking pages causes expensive inter-process interrupts because there might be a read-write entry in some TLB that is now obsolete and has to be shot down, which can only be avoided if the translation is only ever available for the current thread.And the shit you have to copy around the more you're smashing your caches.
>>108499516How can this be implemented, and has any OS implemented this at all?
>>108485246You're retarded, pidfd alone fixes a lot of Unix's retarded design like signals.
>>108477409That sounds like a great idea!I'll make the logo!
>>108499741>How can this be implementedSee Vulkan command buffers.>has any OS implemented this at allI'm not aware of architectures that support thread-local page translations. x64 certainly isn't one of them.
>>108477409>have a dream postyou will never do anything worthwhile in your pathetic life>>108477424>retarded niggerfeeding the OP nigger dream with meaningless jargon
>>108491001>>108499813Same loser
