| 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
| ||
|
Message-Id: <20080217.232829.222344360.davem@davemloft.net> Date: Sun, 17 Feb 2008 23:28:29 -0800 (PST) From: David Miller <davem@...emloft.net> To: unlisted-recipients:; (no To-header on input) Cc: linux-kernel@...r.kernel.org, kaber@...sh.net, netdev@...r.kernel.org Subject: Re: [PATCH 2.6.24 1/1] sch_htb: fix "too many events" situation From: Martin Devera <devik@....cz> Date: Fri, 15 Feb 2008 00:02:56 +0100 > From: Martin Devera <devik@....cz> > > HTB is event driven algorithm and part of its work is to apply > scheduled events at proper times. It tried to defend itself from > livelock by processing only limited number of events per dequeue. > Because of faster computers some users already hit this hardcoded > limit. > This patch uses loops_per_jiffy variable to limit event processing > up to single jiffy interval and then delay remainder to other > jiffy. > > Signed-off-by: Martin Devera <devik@....cz> I think we would be wise to use something other than loops_per_jiffy. Depending upon the loop calibration method used by a particular architecture it can me one of many different things. Some platforms don't even make use of it and thus leave it at it's default value of "1<<12", so using it as a heuristic here is arbitrary at best. -- 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/
Powered by blists - more mailing lists