On Fri, Feb 13, 2009 at 05:49:57PM +0100, Uli Luckas wrote: > On Friday, 13. February 2009, Matthew Garrett wrote: > > Userland ABI would then be a single /dev/inhibit_suspend, > > with the counter being bumped each time an application opens it. It'll > > automatically be dropped if the application exits without cleaning up. > > > > This seems simpler and also avoids any arguments about the naming > > scheme. What am I missing? > Opening and closing an fd sounds like a lot of overhead. Taking and releasing > locks if going to be a called with very highg frequency. I'd go for an ioctl. Is the performance of open() really that bad compared to ioctl()? And what are your tasks doing that this would actually be a noticable performance issue? Userspace should not be taking and releasing these locks with high frequency. It should be doing so in response to events, and events occur infrequently. Given that the implementation in the field is writing strings into a file in sysfs and nobody's complained, I don't think this is a huge concern. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
