From: Peter Chubb <peter@chubb.wattle.id.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Pre-emption patch for IA-64
Date: Fri, 14 Mar 2003 21:57:55 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709806118@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806101@msgid-missing>
>>>>> "Jesse" = Jesse Barnes <jbarnes@sgi.com> writes:
Jesse> Just FYI, I tried 2.5.64 out on my Bug Sur, and it seems to work ok
Jesse> with the following exceptions:
Jesse> o the AT keyboard support seems broken (characters are slow to show
Jesse> up on the screen and are sometimes repeated)
Jesse> o agp support for 460GX causes a link failure
AT keyboard and PS/2 mouse both!
Jesse> But by using a USB keyboard and turning off agp support, I was able to
Jesse> get an SMP+preempt kernel going, and it seems fine.
On a dual McKinley prototype machine I was able to get lockups with
preempt under heavy I/O and cpu load (e.g., make -j4 in glibc). I'm
waiting for production model McKinleys SMP to retry, as I couldn't
reproduce the problem on production-model Itanium 1, and there were no
symptoms that I could debug.
Also FYI, if you're using posix threads in userland, the port of the
next generation library is almost complete, and, with the kernel
preemption patch, will give much lower latencies for heavily threaded
code, depending on exactly what you're doing.
--
Dr Peter Chubb peterc@gelato.unsw.edu.au
You are lost in a maze of BitKeeper repositories, all almost the same.
next prev parent reply other threads:[~2003-03-14 21:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 17:21 [Linux-ia64] Pre-emption patch for IA-64 Mario Smarduch
2003-03-14 21:24 ` David Mosberger
2003-03-14 21:32 ` Jesse Barnes
2003-03-14 21:38 ` Bjorn Helgaas
2003-03-14 21:57 ` Peter Chubb [this message]
2003-03-14 22:07 ` David Mosberger
2003-03-14 22:41 ` Jesse Barnes
2003-03-17 18:11 ` jim
2003-03-27 23:31 ` Mario Smarduch
2003-03-27 23:33 ` Jesse Barnes
2003-03-28 3:58 ` Peter Chubb
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=marc-linux-ia64-105590709806118@msgid-missing \
--to=peter@chubb.wattle.id.au \
--cc=linux-ia64@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