From: Konstantin Kletschke <konsti@ku-gbr.de>
To: linux-kernel@vger.kernel.org
Subject: Re: How do klogd and syslogd influence code execution timing?
Date: Sat, 11 Dec 2004 19:09:46 +0100 [thread overview]
Message-ID: <20041211180946.GA9409@ku-gbr.de> (raw)
In-Reply-To: <20041210162623.1c749f58.akpm@osdl.org>
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
prev parent reply other threads:[~2004-12-11 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 15:21 How do klogd and syslogd influence code execution timing? Konstantin Kletschke
2004-12-11 0:26 ` Andrew Morton
2004-12-11 18:09 ` Konstantin Kletschke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041211180946.GA9409@ku-gbr.de \
--to=konsti@ku-gbr.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox