From: J Sloan <jjs@pobox.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: heads-up: preempt kernel and tux NO-GO
Date: Tue, 27 Nov 2001 17:17:05 -0800 [thread overview]
Message-ID: <3C043B11.2FA17A19@pobox.com> (raw)
Hi -
I have been looking into the tux2 webserver -
Man, what a thing of beauty. A web benchmark
that sends the load on the web server to 150
when running apache results in a load average
of maybe 2 when running tux, and much faster
results to boot - anyway, I digress....
I built 2.4.16+low-latency+preempt+tux2, and
started testing it. To my horror, the webserver
died - I checked the logs and found an oops -
(for your edification, I attach it below)
So, I figured, preempt and low latency don't
mix well - I'll just build a kernel with tux and
preempt.
To my horror, the new kernel without the
low latency patch oopsed immediately as
well, as soon as I started an apachebench
run from a remote testing box.
(for you edification, I include this oops also)
I removed the preempt patch and basically
compiled just 2.4.16+tux, and hammered on
it for several hours - rock solid.
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 -
Thanks & Regards,
jjs
next reply other threads:[~2001-11-28 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 1:17 J Sloan [this message]
2001-11-28 2:12 ` heads-up: preempt kernel and tux NO-GO Oliver Xymoron
2001-11-28 2:23 ` J Sloan
2001-11-28 2:30 ` Andrew Morton
2001-11-28 4:27 ` Robert Love
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=3C043B11.2FA17A19@pobox.com \
--to=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.