Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I'm curious to know more about the goal behind this fork... #2

Open
stux2000 opened this issue Mar 15, 2019 · 0 comments
Open

I'm curious to know more about the goal behind this fork... #2

stux2000 opened this issue Mar 15, 2019 · 0 comments

Comments

@stux2000
Copy link

Hi JBouron,

First off, it looks like pull request 292 must've been a lot of awesome hard work! I'd like to personally thank you for the contribution! (I'm not a minix dev just a fan.)

Now, at the end of the PR you mentioned this fork. I was hoping to find some kind of description that would expand on what you are doing here. Based on the context of the PR I would imagine that you're implementing fine-grained locking for SMP. Is this assumption correct? That said, glancing at the commit descriptions from this fork there seems to be a lot of optimizing and bug fixing going on (more awesome!)

If you don't mind my curiosity, what is your end goal with this fork? Is it focused on SMP or is your aim grander?

Now to digress a little if you have grander aims: Are you familiar with the initial work done to port minix to the Raspberry pi? The wiki page is here. The reason I mention it is that the kernel is supposed to be better organized to make it more platform agnostic, which is a change I'd like to see pushed to the minix master branch before it goes stale. However, the work isn't 100% complete and may or may not conflict with your changes.

Thanks again for all your help! 👍 :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant