MIT-6.828 | This is an implementation of MIT
kandi X-RAY | MIT-6.828 Summary
kandi X-RAY | MIT-6.828 Summary
This is an implementation of MIT 6.828 Operating System Engineering's labs. I am writing blogs on zhihu.com, giving explanation to this implementation. The first blog is Lab1, just in case the previous link doesn't work. This implementation and the blogs do not guarantee correctness of any kind. You are welcome to fork this repository and post bugs on issues. I should remind you of the Collaboration Policy that your professors enforce on you. You should not dishonest or dishonor yourself with the contents of this repository.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of MIT-6.828
MIT-6.828 Key Features
MIT-6.828 Examples and Code Snippets
Community Discussions
Trending Discussions on MIT-6.828
QUESTION
Blow is an implementation of Sieve of Eratosthenes in C
...ANSWER
Answered 2020-Nov-15 at 03:28The code is an adaptation of the paper Coroutine prime number sieve by M. Douglas McIlroy to the Xv6 operating system, a re-implementation of Version 6 Unix used for teaching. The technique is from 1968 as an experiment in co-routines via pipes. The paper explains the algorithm and rationale.
The program implements the sieve of Eratosthenes as a kind of production line, in which each worker culls multiples of one prime from a passing stream of integers, and new workers are recruited as primes are discovered.
When Unix came to be, my fascination with coroutines led me to badger its author, KenThompson, to allow writes in one process to go not only to devices but also to matching reads in another process.
...the coroutine sieve has been a standard demo for languages or systems that support interprocess communication. Implementations using Unix processes typically place the three coroutines—source, cull and sink—in distinct executable files.The fact that the whole program can be written as a single source file, in a language that supports neither concurrency nor IPC, is a tribute not only to Unix’s pipes, but also to its clean separation of program initiation into fork for duplicating address spaces and exec for initializing them.
I believe using stdin and stdout is an artifact of its origins in the early days of Unix when piping stdin and stdout between processes was first introduced. It makes a lot more sense in shell.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install MIT-6.828
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page