From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: Re: RT specifics features
Date: Wed, 10 Dec 2003 11:02:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107105433724490@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107104745718077@msgid-missing>
Ghislain K. schrieb:
>
> Hi All,
>
> I don't know if i write to the right mailing list for my
> problems... but I need quick help. So :
>
> 1) Situation :
> My lab. is benching a IA64 itanium2 quadi-processors platform
> for our Real-Time applications.
>
> 2) What we were intent to do :
> We tried to patch a 2.4.18 from Red Hat Enterprise 2.1 with :
> * Robert Love patch on cpu_affinity,
> * Tim Hockins patch on procstate,
> to isolate alone each ours processes on its CPU.
>
> It doesn't work until now and the quadri must go out our labs the
> 15 dec.
>
> 3) SOS :
> So, I am looking for a "distribution", a tree, a patch, a clue,
> ... to include such features in my kernel or an other.
2.4.18 is pretty old for that features. You might try 2.4.21 + ia64
patch from kernel.org.
Good luck
Christian
prev parent reply other threads:[~2003-12-10 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 9:02 RT specifics features Ghislain K.
2003-12-10 11:02 ` Christian Hildner [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-107105433724490@msgid-missing \
--to=christian.hildner@hob.de \
--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