From: Andrea Arcangeli <andrea@suse.de>
To: Rafal Boni <rafal.boni@eDial.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Gregory Maxwell <greg@linuxpower.cx>
Subject: Re: 2.2.19pre3 and poor reponse to RT-scheduled processes?
Date: Sat, 30 Dec 2000 19:16:39 +0100 [thread overview]
Message-ID: <20001230191639.E9332@athlon.random> (raw)
In-Reply-To: <200012292154.QAA17527@ninigret.metatel.office>; from rafal.boni@eDial.com on Fri, Dec 29, 2000 at 04:54:23PM -0500
On Fri, Dec 29, 2000 at 04:54:23PM -0500, Rafal Boni wrote:
> Now my box behaves much more reasonably... I'll just have to beat harder
> on it and see what happens.
Another thing: while writing to disk if you want low latency readers you can
do:
elvtune -r 1 /dev/hd[abcd]
The 1/2 seconds stalls you see could be just because of applications that waits
I/O synchronously while the elevator is reodering I/O requests (and even if the
elevator wouldn't reorder anything the new requests would go to the end of the
I/O queue so they would have some higher latency anyways). That's normal and if
it's the case to avoid those stalls you can only decrease the I/O load or
increase disk throughput ;). The important thing is that the kernel is
not sitting in a tight kernel loop without reschedule in it during such 2
seconds.
However 2.2.19pre3aa4 includes also the lowlatency bugfixes in case you have
tons of ram and you're sending huge buffers to syscalls.
Andrea
--
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/
prev parent reply other threads:[~2000-12-30 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 20:45 Rafal Boni
2000-12-29 21:19 ` Gregory Maxwell
2000-12-29 21:54 ` Rafal Boni
2000-12-30 18:16 ` Andrea Arcangeli [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=20001230191639.E9332@athlon.random \
--to=andrea@suse.de \
--cc=greg@linuxpower.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rafal.boni@eDial.com \
/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