From: Alex Williamson <alex_williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.4.9 vs 2.4.18 for HPC
Date: Tue, 06 Aug 2002 15:44:02 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905914@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905912@msgid-missing>
To name a few...
- HP zx1 chipset support
- McKinley Perfmon support
- McKinley optimized assembly for copy_user, memcpy, copy_page
Alex
Egan Ford wrote:
>
> With respect to Itanium2 what advantages does 2.4.18 have over 2.4.9 in
> an HPC environment?
>
> My concern is that RH7.2 does not have a 2.4.18/19 kernel and probably
> will not. For support reasons, running 2.4.9-34 from RH may be
> required. I am curious about the possible performance and stability
> issues with 2.4.9 on Itanium2.
>
> I am trying to build a case for software development on 2.4.18/19
> kernel.org kernels.
>
> Thanks.
>
--
Alex Williamson Linux Development Lab
alex_williamson@hp.com Hewlett Packard
970-898-9173 Fort Collins, CO
next prev parent reply other threads:[~2002-08-06 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 15:33 [Linux-ia64] 2.4.9 vs 2.4.18 for HPC Egan Ford
2002-08-06 15:44 ` Alex Williamson [this message]
2002-08-06 15:44 ` Steffen Persvold
2002-08-06 16:19 ` Mike Lang
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-105590701905914@msgid-missing \
--to=alex_williamson@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox