On Wed, Dec 21, 2011 at 06:12:39PM -0800, Tim Bird wrote: > > Again, please see what we are already doing in the kernel and userspace, > > I think a lot of the above is already implemented. > > I don't know what systemd has got going on in user-space. I'm looking > at a very recent kernel, and I see no support for multiple log channels, > or an optimized open/write path. How is the existing syslog read path not "optimized"? What kind of speed and numbers are we talking about here? Oh, and you do know about the userspace printk tty driver, right? What about using that combined with the existing syslog system call? systemd doesn't use it, but I know of a few embedded systems that are already using it today, and I think it might solve the android issues already. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
