public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Smarduch <cms063@email.mot.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Pre-emption patch for IA-64
Date: Fri, 14 Mar 2003 17:21:21 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806101@msgid-missing> (raw)

Hi,
    we're trying to build a reliable low-latency system for use
in telco call processing carrier grade environments (on rx2600
NEBS like servers) . One of the patches we're heavily relying on
is the 'Kernel Preemption' patch. First of we're interested in the
(i) status of this patch on  IA-64 (ii) any issues that you may
have ran into.

Our understanding is that the 'Preemption Patch' offers a systematic
scheduling checkpoint vs. 'low latency patch' which examines
the kernel for any long running code  and based on that
preemption checks are inserted in the kernel proper only (kernel.org)
but addon packages may introduce long latencies. While we plan to
run with 1mS clock tick, low latency  and the preemption
paches, the preemption patch is viewed as a must to gurantee
a bound on 'soft-realtime response'.  Please point out if these
assumption are somewhat correct or is too much emphasis
being placed on the preemption patch, the soft-realtime response
we're looking for is 1mS.

thanks,
    Mario.





             reply	other threads:[~2003-03-14 17:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14 17:21 Mario Smarduch [this message]
2003-03-14 21:24 ` [Linux-ia64] Pre-emption patch for IA-64 David Mosberger
2003-03-14 21:32 ` Jesse Barnes
2003-03-14 21:38 ` Bjorn Helgaas
2003-03-14 21:57 ` Peter Chubb
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-105590709806101@msgid-missing \
    --to=cms063@email.mot.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