On Tuesday 04 August 2009, Alan Stern wrote: > On Tue, 4 Aug 2009, Rafael J. Wysocki wrote: > > > Not only that. I'd like to simplify the design, because IMO using one async > > domain would be much more straightforward than using multiple ones. > > > If I understand the async framework correctly, the domains are only used for > > synchronization, ie. if you want to wait for a group of async operations to > > complete, you can put them all into one domain and then call > > async_synchronize_full_domain() to wait for them all together. > > > > You don't need multiple domains to run multiple things in parallel. > > There's a basic confusion going on here. > > Rui is using "async domain" to mean a collection of devices which > will be suspended or resumed serially. Different domains run in > parallel. > > Rafael is using "async domain" to mean a collection of devices which > will be suspended or resumed in parallel. Different domains run > serially. > > Once that is cleared up, you should be able to communicate a little > better... :-) Well, I tried to follow the naming convention of kernel/async.c. Best, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
