From: Rafal Boni <rafal.boni@eDial.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: 2.2.19pre3 and poor reponse to RT-scheduled processes?
Date: Fri, 29 Dec 2000 15:45:23 -0500 [thread overview]
Message-ID: <200012292045.PAA17190@ninigret.metatel.office> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
[...Please CC me on any replies, as I'm not on the list(s)...]
Folks:
I was experiencing problems with 2.2.16 where the box would go out
to lunch for a few seconds flushing buffer or paging at inopportune
times (is there ever an opportune time for the box to become non-
reponsive for 5 seconds? 8-).
2.2.19pre3 makes the behaviour much better, but I still see ~ 2sec
pauses at times. I'm sending this to the MM list as well, since I
believe the poor behaviour in 2.2.16 was an MM issue... I don't
know where the slowdowns are happening this time around.
The box in question is running the linux-ha.org heartbeat package,
which is a RT-scheduled, mlock()'ed process, and as such should
get as good service as the box is able to mange. Often, under
high disk (and/or MM) loads, the box becomes unreponsive for a
period of time from ~ 1 sec to a high of ~ 2.8sec.
The test is simply running a 'dd if=/dev/zero of=/u1/big-empty-file
bs=1k count=512000 && date'. Generally, the box will sieze up around
the same time as the the 'dd' finishes (maybe trying to exec date?).
I'd appreciate any hints at how to reduce the non-reponsiveness
window down as much as possible. I haven't yet looked to see if
there is a version of the low-latency patches for 2.2.18 or 19pre,
but I'd appreciate other ideas on tracking this down as well.
Thanks!
- --rafal
- ----
Rafal Boni rafal.boni@eDial.com
PGP key C7D3024C, print EA49 160D F5E4 C46A 9E91 524E 11E0 7133 C7D3 024C
Need to get a hold of me? http://800.eDial.com/rafal.boni@eDial.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE6TPfjEeBxM8fTAkwRAiPaAKDSp1udFSypqq838fwAjQnlFW0m2wCgtycm
xF7xuBroSl3YXCTqUXGDAy0=
=JHLL
-----END PGP SIGNATURE-----
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next reply other threads:[~2000-12-29 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 20:45 Rafal Boni [this message]
2000-12-29 21:19 ` Gregory Maxwell
2000-12-29 21:54 ` Rafal Boni
2000-12-30 18:16 ` Andrea Arcangeli
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=200012292045.PAA17190@ninigret.metatel.office \
--to=rafal.boni@edial.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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