On Sun, Aug 23, 2015 at 02:02:30AM +0200, Cyril Brulebois wrote: > > > $ grep ioctl log | wc -l > > 14035 > > OVER 9000 ioctls! Are you kidding me?
Console-setup is definitely not THAT slow. Unless your directory /etc/console-setup/ doesn't contain a cached keymap in which case ckbcomp has to be invoked. And yes - in this case it does use about 14000 ioctls. In my opinion, such results imply that the testing environment used for these results has not been configured properly. Things are not as bad as you think they are. :) > > $ grep 'open\|read\|stat' log | wc -l > > 3881 > > OVER 3000 filesystem related syscalls. That all is needed to just > > configure the console? Seriously? > > > > Please find a way to cut down this activity, there must be a way to > > do that. > > Patches welcome. Or maybe no pathes are needed... The general plan for console-setup must be to move the entire console configuration in the initrd. Console-setup already provides good and easy to use support for the initrd builders. Dracut already includes a script provided by console-setup (BTW, it is fast and simple...). It is only because of my lasiness that I haven't submitted wishlist bug reports for the other initrd-builders. If the console is configured, then the main scripts of console-setup don't have to reconfigure the console again. Right now they do reconfigure it but it is in my TODO list to fix this. Anton Zinoviev
