I'm one of the team at Azul working on these kernel-side changes. You're right, we haven't talked with many folks about our enhancements yet. While we have had discussions with some in the kernel community, we've been unable to discuss our enhancements in the wider audience until the Managed Runtime Initiative was launched.
We realize the kernel code we've just published as part of MRI is not yet ready for prime time, and will take iterations to wend its way upstream. Right now, the code should be considered a basis for discussion. It'd be good to have the conversation about the types of problems we're solving, and how we might improve our solutions.
Until MRI kernel changes are perceived as solving a general problem in an acceptable, maintainable way, they're not going to be accepted by the Linux community. That's fine, and it's why we published the code this week--so we could start talking about it.
And, yeah, we know that facilities like pluggable memory managers and schedulers are...uh...contentious. We thought this packaging was a bit more comprehensible than inline changes to all of the mm and sched code.