Messages in this thread | | | Date | Sun, 12 Jun 2005 00:56:41 -0400 | From | Karim Yaghmour <> | Subject | Re: [PATCH] local_irq_disable removal |
| |
Daniel Walker wrote: >>The proof is in the pudding: it's not for nothing that the results >>we published earlier show that the mere enabling of Adeos actually >>increases Linux's performance under heavy load. > > > Why do you think that is? Is ADEOS optimized for specific machine > configurations?
I was refering back to what you were talking about just before I replied: no disabling of interrupts.
> It doesn't seem like one could really merge the two. From what I've read > , it seem like ADEOS is something completly indepedent . It would be linux > and ADEOS , but never just linux .
I'm not sure I follow. Forget about all the fancy hypervisor/ nanokernel talk. The bottom line is that while the initial design called for an entire nanokernel, the actual code in adeos can be summarized by the interrupt pipepline. Said ipipe is a feature that stands on its own and could easily be integrated into mailine as a feature. Using just the ipipe, for example, it would be possible to load a module that would register ahead of Linux in the pipeline and therefore obtain its interrupts regardless of whether or not Linux has stalled its pipeline stage (i.e. cli'ed.) That's hard-rt at a very low cost in terms of general kernel source code intrusion.
This is why I have a hard time understanding the statement that "It would be Linux and Adeos, but never just Linux." In this case, it would be Linux with an ipipe. Said ipipe can then be left unpopulated, and then we get back to what you guys have just implemented. Or a driver can use it to obtain hard-rt. Or additional Adeos components can hook onto the ipipe to provide services enabling RTAI to run side-by-side with Linux.
May I suggest getting a copy of a recent Adeos patch and looking through it? I'm sure it would make things much simpler to understand.
Karim -- Author, Speaker, Developer, Consultant Pushing Embedded and Real-Time Linux Systems Beyond the Limits http://www.opersys.com || karim@opersys.com || 1-866-677-4546 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |