Hacker News new | ask | show | jobs
by anttiok 3792 days ago
If it's not an instance of a selection of components running on top of externally scheduled threads, it's not a rump kernel in my book. So, strictly speaking no, but the answer really depends on what you want to convey by "basically". Many of the use cases should fit both projects.
2 comments

I've been working (though it's too slow) on making answer to this question "yes".

https://github.com/thehajime/blog/issues/1

I don't know enough about rump to talk more definitively, and in fact I've failed to find an overview about what it is technically, how it works on NetBSD, how it works outside NetBSD, etc. Does running rump on Linux provide the SMP scalability improvements one misses with NetBSD's kernel for instance? Can you point me at something to read that's short enough to digest in an hour?
Follow the "Getting Started" link on rumpkernel.org. That page includes both short and long reading (should you get more interested ;), and also some "hands on" tutorials should you learn about things better that way (I know I do).

SMP scalability is all about bottlenecks. If the driver is the bottleneck, it won't scale no matter where you run it.