From: "Peter Maas" <peter@goquest.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Busy-wait delay in qmail 1.03 after upgrading to Linux 2.6
Date: Mon, 19 Jan 2004 23:51:09 -0600 [thread overview]
Message-ID: <000501c3df19$6769cfb0$6600a8c0@pixl> (raw)
Re: Haakon Riiser
>I think I've been able to create a simple test program that
>demonstrates the bug I encountered with Qmail.
I've compiled and tested the code you posted, i thought that i would add
that renicing the LISTENER processes shows some interesting effects.
at nice 0 the writer spits out about 40 writes under .01 ms, then 3 to 5
writes at 97+ ms, after about 3 minutes its starts to get more random.
at nice -1 the writer spits out about 40 writes under .01 ms, then about 40
writes at 97+ ms, kept this cycle for over 10 minutes.
at nice 1 the writer spits out a few hundred writes under .01 ms, and
occasionally one at 97+ ms.
same effect if elevator=deadline
This thread caught my intrest because I run qmail on this box.
Peter Maas
Pentium II - 400MHz 128MB PC100
kernel-2.6.1-1.126 from http://people.redhat.com/arjanv/2.6/
(not subscribed - reads archives)
next reply other threads:[~2004-01-20 5:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 5:51 Peter Maas [this message]
[not found] <20040120021353.39e9155e.akpm@osdl.org>
2004-01-20 18:33 ` Fw: Re: Busy-wait delay in qmail 1.03 after upgrading to Linux 2.6 Manfred Spraul
2004-01-20 19:22 ` Haakon Riiser
2004-01-20 19:45 ` Mike Fedyk
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 21:09 Haakon Riiser
2004-01-13 21:51 ` Andrew Morton
2004-01-13 23:26 ` Haakon Riiser
2004-01-13 23:43 ` Andrew Morton
2004-01-14 0:07 ` Haakon Riiser
2004-01-14 11:29 ` Haakon Riiser
2004-01-20 0:46 ` Haakon Riiser
2004-01-13 23:46 ` Haakon Riiser
2004-01-14 0:06 ` Andrew Morton
2004-01-14 10:27 ` Giuliano Pochini
2004-01-14 11:20 ` Haakon Riiser
2004-01-15 0:12 ` Haakon Riiser
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='000501c3df19$6769cfb0$6600a8c0@pixl' \
--to=peter@goquest.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.