From: Patrik Hagglund <patha@softlab.ericsson.se>
To: linux-kernel@vger.kernel.org
Subject: SCHED_FIFO/SCHED_RR in 2.4 vs 2.2
Date: Wed, 17 Jan 2001 15:21:31 +0100 [thread overview]
Message-ID: <20010117142125.D4F2E583A@hunny.softlab.se> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
I have a server program that communicates with a number of client
programs via TCP sockets. I have tried to measure the response time
of the server program by using a program similar to tcpdump (that
uses a packet socket).
However, when I run the server program on 2.4.0 within a
SCHED_FIFO or SCHED_RR scheduling class (instead of SCHED_OTHER)
the average response time gets better (and is more predictable)
but I occasionally get delays that seems to be multiples of 2
seconds, in the range of 2 to 26 seconds. I don't get this
behavior with 2.2.18.
Does anybody have some idea why I get this strange behavior on 2.4.0?
--
Patrik Hägglund
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2001-01-17 14:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010117142125.D4F2E583A@hunny.softlab.se \
--to=patha@softlab.ericsson.se \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®