Hi, Jason, Glad you made it back to SA OK!
On Apr 28, 2010, at 8:00 , Jason Manley wrote:
The logs you're seeing are likely from the kernel itself, as BORPH logs every bus transaction. A kernel recompile is required to remove this entirely. But you can configure what is logged to disk by syslog in /etc/syslog.conf. Perhaps try to disable the logging of these messages.
Commenting these lines out of /etc/syslog.conf may eliminate the delays caused by syslog writing to disk, but it does not eliminate the delays of the kernel logging to syslog. As you point out, a recompile of the kernel is necessary to remove this entirely, If it isn't already, it would be very nice to have borph's logging level be a kernel parameter that could be set at boot time to allow for logging when needed, but skip logging when not needed. In the interim, it would be nice to have two pre-built kernels: one with logging and one without logging. Those who would otherwise throw away the borph (and other?) kernel messages would certainly be better off if their kernel never generated the messages in the first place.
You should be getting around 7MegaBytes/s across that bus.
56 Mb / 16 b < 4 MHz << bus clock frequency Seems like a lot of room for improvement there even with bus overhead. Dave
