From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Scheduler fairness problem on 2.6 series
Date: Thu, 12 Aug 2004 10:08:22 +0200 [thread overview]
Message-ID: <411B2576.6010903@gmx.de> (raw)
In-Reply-To: <411AAEDA.9070601@kolivas.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Con Kolivas wrote:
| Prakash K. Cheemplavam wrote:
|
|> 124910 9.8170 vmlinux tcp_poll
|> 123356 9.6949 vmlinux sys_select
|> 85634 6.7302 vmlinux do_select
|> 71858 5.6475 vmlinux sysenter_past_esp
|> 62093 4.8801 vmlinux kfree
|> 51658 4.0600 vmlinux __copy_to_user_ll
|> 37495 2.9468 vmlinux max_select_fd
|> 36949 2.9039 vmlinux __kmalloc
|> 22700 1.7841 vmlinux __copy_from_user_ll
|> 14587 1.1464 vmlinux do_gettimeofday
|>
| It looks like your select timeouts are too short and when the cpu load
| goes up they repeatedly timeout wasting cpu cycles.
| I quote from `man select_tut` under the section SELECT LAW:
|
| 1. You should always try use select without a timeout. Your program
| should have nothing to do if there is no data available. Code
| that depends on timeouts is not usually portable and difficult
| to debug.
|
Thanks for your explanation. I cannot do anything about it, as it is
mpich related. So I'll ask them if they could change its behaviour a bit
so that it eats less CPU on a single CPU machine.
Cheers,
Prakash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBGyV1xU2n/+9+t5gRAqHEAJ9hW/AJYtMenL6mXQ4JZYvTvRrRkgCdHwQD
LbJ1MYJ/pbpNbrT8vvlD8uI=
=9AUE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-08-12 8:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040811010116.GL11200@holomorphy.com>
2004-08-11 2:21 ` Scheduler fairness problem on 2.6 series (Attn: Nick Piggin and others) spaminos-ker
2004-08-11 2:23 ` William Lee Irwin III
2004-08-11 2:45 ` Peter Williams
2004-08-11 2:47 ` Peter Williams
2004-08-11 3:23 ` Peter Williams
2004-08-11 3:31 ` Con Kolivas
2004-08-11 3:46 ` Peter Williams
2004-08-11 3:44 ` Peter Williams
2004-08-13 0:13 ` spaminos-ker
2004-08-13 1:44 ` Peter Williams
2004-08-11 3:09 ` Con Kolivas
2004-08-11 10:24 ` Prakash K. Cheemplavam
2004-08-11 11:26 ` Scheduler fairness problem on 2.6 series Con Kolivas
2004-08-11 12:05 ` Prakash K. Cheemplavam
2004-08-11 19:22 ` Prakash K. Cheemplavam
2004-08-11 23:42 ` Con Kolivas
2004-08-12 8:08 ` Prakash K. Cheemplavam [this message]
2004-08-12 18:18 ` Bill Davidsen
2004-08-12 2:04 ` Scheduler fairness problem on 2.6 series (Attn: Nick Piggin and others) spaminos-ker
2004-08-12 2:24 ` spaminos-ker
2004-08-12 2:53 ` Con Kolivas
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=411B2576.6010903@gmx.de \
--to=prakashkc@gmx.de \
--cc=kernel@kolivas.org \
--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.