[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100809072618.GB1586@ucw.cz>
Date: Mon, 9 Aug 2010 09:26:18 +0200
From: Pavel Machek <pavel@....cz>
To: david@...g.hm
Cc: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
arve@...roid.com, mjg59@...f.ucam.org, florian@...kler.org,
rjw@...k.pl, stern@...land.harvard.edu, swetland@...gle.com,
peterz@...radead.org, tglx@...utronix.de, alan@...rguk.ukuu.org.uk,
menage@...gle.com, david-b@...bell.net, James.Bottomley@...e.de,
tytso@....edu, arjan@...radead.org, swmike@....pp.se,
galibert@...ox.com, dipankar@...ibm.com
Subject: Re: Attempted summary of suspend-blockers LKML thread, take two
Hi!
> >I should have asked this earlier... What exactly are the apps'
> >compatibility constraints? Source-level APIs? Byte-code class-library
> >invocations? C/C++ dynamic linking? C/C++ static linking (in other
> >words, syscall)?
>
> For Java/Dalvik apps, the wakelock API is pertty high level -- it
> talks to a service via RPC (Binder) that actually interacts with the
> kernel. Changing the basic kernel<->userspace interface (within
Strange. Arve claimed that open/close is too slow, and few
microseconds faster ioctl is needed, and now we learn it actually uses
RPC.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists