[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Proposal for init/kexec/hotplug format for Xen
Keir Fraser wrote: The IDC primitives are likely to be *so* low level that this will be a non-issue. Anything that can needs to be fault-tolerance aware in any way I think will be in higher layers.Really the libidc is almost a no-op -- we have shared memory and notifications -- semaphores and message queues on top of that is very little code. I agree. You sound like you are more worried about the device-channel setup/teardown/probe/recovery code. That would be above libidc, if we use libidc at all. I'm currently prototyping a semaphore mechanism. One of the nice things I realized is that if a message queue uses semaphores, then something like xcs is unnecessary. What I'm thinking about right now is how to assign out ports for notification. It's somewhat non-trivial to figure out the best way to manage that. Any thoughts? Regards, Anthony Liguori ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |