From: "Jack O'Quin" <joq@io.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Florian Schmidt <mista.tapas@gmx.net>,
Andrew Burgess <aab@cichlid.com>,
linux-kernel@vger.kernel.org, jackit-devel@lists.sourceforge.net
Subject: Re: [Jackit-devel] Re: Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.31-19
Date: 02 Dec 2004 14:48:23 -0600 [thread overview]
Message-ID: <87zn0wctpk.fsf@sulphur.joq.us> (raw)
In-Reply-To: <1102018036.31206.8.camel@krustophenia.net>
Lee Revell <rlrevell@joe-job.com> writes:
> On Thu, 2004-12-02 at 11:07 -0600, Jack O'Quin wrote:
> > Is printk() guaranteed not to wait inside the kernel? I am not
> > familiar with its internal implementation.
>
> Yes. It just writes to a ring buffer and klogd dumps this to syslog.
> So if you really start to spew printk's they don't all make it to the
> log but you never get blocked.
>
> The implementation probably looks a lot like a correct solution to fix
> the printf-from-RT-context issue in JACK would.
Right. That's exactly what I have in mind, whenever I find time to
work on it. :-)
There's some similar code I wrote for JAMin, which we could adapt.
--
joq
next prev parent reply other threads:[~2004-12-02 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 15:46 Andrew Burgess
2004-12-02 16:03 ` [Jackit-devel] " Florian Schmidt
2004-12-02 16:26 ` Jack O'Quin
2004-12-02 16:57 ` Florian Schmidt
2004-12-02 17:07 ` Jack O'Quin
2004-12-02 20:07 ` Lee Revell
2004-12-02 20:48 ` Jack O'Quin [this message]
2004-12-02 17:09 ` Florian Schmidt
2004-12-02 17:32 ` Jack O'Quin
2004-12-02 20:03 ` Florian Schmidt
2004-12-02 21:10 ` Florian Schmidt
2004-12-02 22:34 ` Bill Huey
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=87zn0wctpk.fsf@sulphur.joq.us \
--to=joq@io.com \
--cc=aab@cichlid.com \
--cc=jackit-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mista.tapas@gmx.net \
--cc=rlrevell@joe-job.com \
/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
all inboxes | Powered by JetHome®