From: Robert Love <rml@tech9.net>
To: J Sloan <jjs@pobox.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: heads-up: preempt kernel and tux NO-GO
Date: 27 Nov 2001 23:27:32 -0500 [thread overview]
Message-ID: <1006921653.824.2.camel@phantasy> (raw)
In-Reply-To: <3C043B11.2FA17A19@pobox.com>
In-Reply-To: <3C043B11.2FA17A19@pobox.com>
On Tue, 2001-11-27 at 20:17, J Sloan wrote:
> So, there is an issue with tux and the preempt
> patch - I've got big plans for tux atm, so for
> now I will have to do without preempt -
Tux makes heavy use of per-CPU data and some of it is undoubtedly not
preempt-safe. It is probably trivial to fix but would take some
familiarity with the codebase...Ingo would know best. Its not on the
top of my todo list, but I will look into it.
Robert Love
next prev parent reply other threads:[~2001-11-28 4:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 1:17 heads-up: preempt kernel and tux NO-GO J Sloan
2001-11-28 2:12 ` Oliver Xymoron
2001-11-28 2:23 ` J Sloan
2001-11-28 2:30 ` Andrew Morton
2001-11-28 4:27 ` Robert Love [this message]
2001-11-29 4:11 ` data point: tux and low-latency patches OK J Sloan
2001-11-29 1:18 ` interrupt ? McEnroe
2001-11-29 17:07 ` Robert Love
2001-11-29 21:03 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 1:21 heads-up: preempt kernel and tux NO-GO J Sloan
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=1006921653.824.2.camel@phantasy \
--to=rml@tech9.net \
--cc=jjs@pobox.com \
--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