Messages in this thread | | | Date | Sat, 11 Dec 2004 19:09:46 +0100 | From | Konstantin Kletschke <> | Subject | Re: How do klogd and syslogd influence code execution timing? |
| |
Am 2004-12-10 16:26 -0800 schrieb Andrew Morton: > > The difference is that if klogd is running, a printk() will cause a wakeup
Hm, good that I asked. I know now, the difference is the _running_ klogd...
> to go into the scheduler code, take and release locks, take more time, etc.
scheduler code... take/release locks... I think that works around a Bug or problem we have in our driver code... But I will have to search for it since I am a greenhorn in writing device drivers and locking/protecting critical sections :)
Regards, Konsti
-- GPG KeyID EF62FCEF Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |