Well, Andi Kleen reported that serial_in appears in his boot time
profile after a boot.
Depending on the baud rate used, serial console printk spends time
spinning waiting for the serial port to send characters. The slower
the baud rate, obviously the longer it spins.
Andi tried to suggest ways to make serial console asynchronous so we
didn't have to spin, but any solution in that direction means that we:
a) have to rely on interrupts running
b) have to buffer the data somewhere, which may possibly fill up and
then what do we do with the printk message
Bear in mind that dropping random printk messages because we've filled
a buffer isn't acceptable. Also note that the behaviour in this area
hasn't changed since 2.4 times.
Obviously, the way to reduce the time spent writing console messages to
the serial port is to increase the baud rate. 8)
-- Russell King (email@example.com) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/