I'm currently only able to read ~100kB/s from shared BRAMs on the ROACH. I assume the ROACH can do better than this.
I've profiled my code and am certain that the bottleneck is in reading BRAM files. When I looked closer, I found a bunch of logging showing up in /proc/kmsg for every file transaction. Acting on the theory that this logging was slowing everything down, I killed syslogd and klogd (/etc/init.d/klogd stop, etc). Yet I still get lines in /proc/kmsg from "proc_borph". I can't find any processes that I recognize as potentiall logging daemons, and I haven't found anything with lsof that indicates what may be writing to /proc/kmsg. I'm left thinking that maybe this logging is compiled into the kernel. Does anyone know what is cause such lousy file I/O performance on the ROACH? If it is indeed a problem with excessive logging, how do I stop it? -- Aaron Parsons 510-406-4322 (cell) Campbell Hall 523, UCB
