On Mon, Aug 09, 2010 at 08:18:22PM +0100, Alan Cox wrote:
It is a sad day on LKML when we are busy digging pits for each other.
On the other hand, I have seen far sadder days, and the pit you dug
happens to lead somewhere useful. As Brian noted in his reply, the
situation you call out can occur with manual suspend-to-RAM already:
the fact is that this is a design choice. You could indeed make a
PM-driving office application if you wished, or run the same application
as a power-oblivious application. There is a slight difference in the
contract with the user. Of course, it is quite clear which one -you-
prefer, but preferences can vary.
Android is certainly where suspend blockers originated, and is to the best
of my knowledge is still the only platform that uses them. But there is
a first user of every new mechanism, and for some time that first user
will by definition be the only user of that mechanism. So the fact
that Android is most probably the only user of suspend blockers does
not prove anything about whether or not suspend blockers are sensible.
Indeed, people have played games on their cellphones for some years.
Not sure whether any of the games resembles World of Warcraft, but they
probably soon will. If so, perhaps they will make use of significant
hardware acceleration -- most other embedded systems do so.
But that doesn't guarantee that solutions developed for PCs and laptops
will be optimal (or even usable) on cellphones. Sufficient difference
in scale can easily change the form of the optimal solution, so you
have not yet made your case. (For that matter, you also haven't proven
that adoption of suspend blockers or something like them depends on the
assumption that cellphones are special.)
I hope that no one is arguing that Android will remain unchanged, just
as I hope no one would argue that Linux will remain unchanged. In fact,
I am quite confident that both Linux and Android will continue to change.
So exactly what point were you attempting to make here?
As to busting all apps, lthough there have been situations where busting
all the apps turned out to be the right thing to do, I agree that these
situations are extremely rare. Such situations are usually associated
with the emergence of a new high-volume platform.
From what I can see, the Android developers are suffering less than
the PC developers were suffering when the PC was the same age that
Android is now. For that matter, suspend blockers don't put detailed
awareness of platform behavior into apps. You must look to the heavily
power-optimized apps to find that kind of awareness.
Hmmm... Exactly which part do you consider flawed? Let's take it
one sentence at a time. The devices that I know of that lack suspend
blockers also lack opportunistic suspend. Therefore, all applications on
such devices run as would an application that acquired a suspend blocker
when it started and did not release that suspend blocker until it exited.
Pretty straightforward.
As for the first part of the second sentence, you yourself have argued
that each and every application should be carefully written to avoid
battery drain (or, equivalently, to promote energy efficiency), so
presumably the flaw does not reside there. That leaves the second
half of that sentence, for which we both must defer to Ted. But Ted's
intended meaning of his King Canute analogy does not affect the argument
as to whether or not suspend blockers (or, again, something like them)
are useful.
I really do like this progression. I will return to it further down.
The OS can be said to possess the full picture only if the applications
communicate their portion of the picture to the OS. Linux has quite a
few APIs devoted to this sort of communication, many of them mandated
by POSIX. Some people are proposing suspend blockers (or something like
them) as another member of this set of APIs.
And there are numerous environments in which it will not run. So what?
And if the work has not been done on the application, and if there is
nothing like suspend blockers, the OS cannot do its job. So how exactly
does this support your position?
Which brings us to the progression from DOS to Windows 3.x to Real
OS. Why can the Real OS's scheduler can operate "in a manner which
prevents CPU hogs from breaking the system or abusing it sufficiently
to threaten its functionality" while still allowing applications with
special requirements to operate correctly? One reason is the advent
of any number of APIs that communicate special properties of specific
applications to the OS, including the old nice() system call, POSIX
realtime, numerous facilities to communicate application properties to
the VM system, and so on.
Given this context, are you sure that suspend blockers are not the next
step in the Real OS progression? Or some QoS mechanism that subsumes
suspend blockers? However, there is a lot of negative experience
around general-purpose QoS mechanisms -- you have to be quite careful
in order to avoid spending more energy computing QoS than you would
otherwise spend on the application's computations. The usual way out of
this trap is to abandon generality in favor of exploiting the commonly
occurring special cases. For all I know, raw suspend blockers might be
the appropriate special case.
Hmmm... I do like "Absolutum Obsoletum", especially if it really does
translate to "If it works it's out of date." However, I am not at all
convinced that it supports your position! ;-)
Thanx, Paul
--
