From: Ray Bryant <raybry@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Preempt problems
Date: Fri, 14 Feb 2003 21:04:52 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805858@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805801@msgid-missing>
Stephane,
We're using a 2.4.19 kernel with a number of patches and SGI fixes, and
some backports from 2.5, as well as our machine
specific stuff. A more complete description of what we run is:
--2.4.19 from www.kernel.org
--IA64 patch
--Atlas patches including discontinguous memory support, VM support
--O(1) scheduler -- including some fixes for large CPU counts, etc
--SGI machine specific H/W support
--SGI patches and fixes for bugs and scalability
--PAGG
--CSA (Comprehensive System Accounting)
--XSCSI (our version of SCSI support from IRIX -- this is a
module/closed source)
Of interest for this discussion is the O(1) scheduler and perfmon.
If you could send me your patch, I will take a look at it and see what
applies.
We will eventually be going to RHAS, but at the moment we are running a
"free-bytes" clone of RH 7.2.
I understand exactly why you are trying to keep the number of variations
small.
Thanks,
Stephane Eranian wrote:
>
> Ray,
>
> On Fri, Feb 14, 2003 at 02:05:53PM -0600, Ray Bryant wrote:
> >
> > Does the deadlock you describe here look at all like the bug report that
> > Jack Steiner has submitted for our Altix kernel?
> > (We're using the O(1) scheduler and pfmon.) (It certainly sound
> > similar.) Details attached.
> >
> > Is anyone working this issue that you know of?
> >
> This problem was reported to me by Intel and others. It was affecting
> the 2.5 kernel only. However given that RHAS 2.1 is also using the
> O(1) scheduler, I had to fix it in 2.4.18/RHAS. I don't exactly
> know which kernel you are using at SGI. Note that the fix has been
> propagated to 2.5.60 as well. I can provide the patch to you but
> note that it also includes updates to perfmon to bring it closer
> to what we have in 2.4.20. My goal is to minimize the number of
> variations out there ;->
>
> --
> -Stephane
--
Best Regards,
Ray
-----------------------------------------------
Ray Bryant
512-453-9679 (work) 512-507-7807 (cell)
raybry@sgi.com raybry@austin.rr.com
The box said: "Requires Windows 98 or better",
so I installed Linux.
-----------------------------------------------
prev parent reply other threads:[~2003-02-14 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 20:17 [Linux-ia64] Preempt problems Peter Chubb
2003-02-03 21:36 ` Stephane Eranian
2003-02-03 22:33 ` Peter Chubb
2003-02-03 23:43 ` David Mosberger
2003-02-05 17:03 ` Joel GUILLET
2003-02-14 20:05 ` Ray Bryant
2003-02-14 20:11 ` Stephane Eranian
2003-02-14 21:04 ` Ray Bryant [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=marc-linux-ia64-105590709805858@msgid-missing \
--to=raybry@engr.sgi.com \
--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 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.