[systemd-devel] Communicating need
Scott James Remnant
scott at netsplit.com
Mon May 16 14:43:28 PDT 2011
On Mon, May 16, 2011 at 2:23 PM, Lennart Poettering
<lennart at poettering.net>wrote:
> Our entire userspace bootup takes <1s here on an older X300. I think
> nobody expects that the mouse reacts any quicker than that.
>
> Your "older X300" is probably rather more powerful than a single-core Atom
CPU.
> But as mentioned elsewhere: if this really is a problem we could modify
> udev trigger to sort the devices according to some user specific rules
> before triggering them. That way we can ensure that input gets triggered
> before network, or whatever else you want to express.
>
> But again, I'd really like to see this profiled before look into
> this. Right now if userspace booting takes < 1s this should be more then
> sufficiently good for desktop machines, include ChromeOS machines.
>
> It depends what you mean by "userspace booting".
We are able to start the entire system, X server and Chromium browser in
about 2.2s
It takes about 5-6s for udev to run input_id on the keyboard + touchpad, and
thus for them to be available to X.
Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20110516/05a65dde/attachment.htm>
More information about the systemd-devel
mailing list