linux-kernel - RE: Very long startup time for a new thread

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 17 Jul 2006 10:44:58 +0200
From:	"Mikael Starvik" <mikael.starvik@...s.com>
To:	"Mikael Starvik" <mikael.starvik@...s.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: RE: Very long startup time for a new thread

Thanks to all that have made suggestions. Finnaly we found that 

#define MIN_TIMESLICE 5
#define DEF_TIMESLICE 25

works much better for us. Maybe it is an effect of that we have HZ=100 ?

/Mikael

-----Original Message-----
From: Mikael Starvik [mailto:mikael.starvik@...s.com] 
Sent: Thursday, July 13, 2006 8:08 AM
To: 'Linux Kernel Mailing List'
Subject: Very long startup time for a new thread

(This is on a 200 MIPS embedded architecture).

On a heavily loaded system (loadavg ~4) I create a new pthread. In this
situation it takes ~4 seconds (!) before the thread is first scheduled
in (yes, I have debug outputs in the scheduler to check that). In a 2.4
based system I don't see the same thing. I don't have any RT or FIFO
tasks. Any ideas why it takes so long time and what I can do about it?

Appreciate any help
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/