From: Denys Fedoryschenko <denys@visp.net.lb>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Jorge Bastos <mysql.jorge@decimal.pt>,
netdev@vger.kernel.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [BUG #12364] Re: HTB - very bad precision? HFSC works fine! 2.6.28
Date: Fri, 9 Jan 2009 12:32:09 +0200 [thread overview]
Message-ID: <200901091232.09923.denys@visp.net.lb> (raw)
In-Reply-To: <20090109103030.GI4605@ff.dom.local>
HZ still matter? With tickless kernel and hrtimers?
On Friday 09 January 2009 12:30:30 Jarek Poplawski wrote:
> On Thu, Jan 08, 2009 at 11:57:13PM +0200, Denys Fedoryschenko wrote:
> > Can 100HZ be issue?
>
> Generally, if you need precise scheduling HZ=1000 should be used if
> higher cpu usage isn't a problem.
>
> Jarek P.
next prev parent reply other threads:[~2009-01-09 10:32 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 22:02 HTB - very bad precision? HFSC works fine! 2.6.28 Denys Fedoryschenko
[not found] ` <008201c97115$091b5d50$1b5217f0$@jorge@decimal.pt>
2009-01-07 22:36 ` Denys Fedoryschenko
[not found] ` <00a101c97118$e25a6ae0$a70f40a0$@jorge@decimal.pt>
2009-01-07 22:44 ` Denys Fedoryschenko
2009-01-07 23:42 ` mysql.jorge
2009-01-08 9:42 ` [BUG 12364] " Jarek Poplawski
2009-01-08 9:54 ` [BUG #12364] " Jarek Poplawski
2009-01-08 10:06 ` Jarek Poplawski
2009-01-08 10:35 ` mysql.jorge
2009-01-08 11:04 ` Jarek Poplawski
2009-01-08 11:22 ` mysql.jorge
2009-01-08 13:59 ` Jarek Poplawski
2009-01-08 14:09 ` mysql.jorge
2009-01-08 17:27 ` mysql.jorge
2009-01-08 18:32 ` Denys Fedoryschenko
2009-01-08 18:37 ` Jorge Bastos
2009-01-08 18:46 ` Denys Fedoryschenko
2009-01-08 18:41 ` Denys Fedoryschenko
2009-01-08 21:46 ` Jorge Bastos
2009-01-08 21:57 ` Denys Fedoryschenko
2009-01-08 22:04 ` Jorge Bastos
2009-01-09 10:30 ` Jarek Poplawski
2009-01-09 10:32 ` Denys Fedoryschenko [this message]
2009-01-09 10:44 ` Jarek Poplawski
2009-01-09 10:47 ` Jorge Bastos
2009-01-09 10:58 ` Jarek Poplawski
2009-01-12 7:27 ` Patrick McHardy
2009-01-12 8:13 ` Jarek Poplawski
2009-01-12 9:49 ` Jorge Bastos
2009-01-12 11:14 ` Jarek Poplawski
2009-01-12 8:30 ` Denys Fedoryschenko
2009-01-12 18:38 ` Denys Fedoryschenko
2009-01-12 19:58 ` Jesper Dangaard Brouer
2009-01-12 20:01 ` Denys Fedoryschenko
2009-01-13 4:33 ` Patrick McHardy
2009-01-13 7:28 ` Stephen Hemminger
2009-01-13 7:52 ` Eric Dumazet
2009-01-13 8:43 ` Michal Soltys
2009-01-13 9:53 ` Jarek Poplawski
2009-01-13 10:08 ` Denys Fedoryschenko
2009-01-12 9:48 ` Jorge Bastos
2009-01-14 1:53 ` Denys Fedoryschenko
2009-01-14 19:37 ` Jorge Bastos
2009-01-15 10:38 ` Jarek Poplawski
2009-01-09 9:48 ` Jarek Poplawski
2009-01-09 9:51 ` Jorge Bastos
2009-01-09 10:06 ` Jarek Poplawski
2009-01-09 10:10 ` Jorge Bastos
2009-01-09 7:24 ` Jarek Poplawski
2009-01-09 9:39 ` Jorge Bastos
2009-01-09 10:02 ` Jarek Poplawski
2009-01-09 7:54 ` Jarek Poplawski
2009-01-09 9:42 ` Jorge Bastos
2009-01-09 10:12 ` Jarek Poplawski
2009-01-09 10:15 ` Jorge Bastos
2009-01-09 10:22 ` Jarek Poplawski
2009-01-09 10:26 ` Jorge Bastos
2009-01-09 10:32 ` Jorge Bastos
2009-01-08 10:37 ` mysql.jorge
2009-01-08 10:34 ` [BUG 12364] " mysql.jorge
2009-01-08 9:27 ` Jarek Poplawski
2009-01-08 9:34 ` Denys Fedoryschenko
2009-01-08 10:40 ` Jarek Poplawski
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=200901091232.09923.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jarkao2@gmail.com \
--cc=mysql.jorge@decimal.pt \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).