On Mon, 16.05.11 14:43, Scott James Remnant (sc...@netsplit.com) wrote: > On Mon, May 16, 2011 at 2:23 PM, Lennart Poettering > <lenn...@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.
It probably is, but it's not a superduper fast CPU either. > > 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". systemd booting a reasonably complete GNOME system (cups, ck, pk, gdm, all that stuff). The time that passes from systemd being invoked until systemd has nothing more to do. I presume a much bigger set of components than on ChromeOS. > It takes about 5-6s for udev to run input_id on the keyboard + touchpad, and > thus for them to be available to X. How come this takes so long? Does this actually delay X? Nromally X should be fine without kbd/mouse and then be able to make use of it the moment it becomes available? Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
