From: jamal <hadi@cyberus.ca>
To: Patrick McHardy <kaber@trash.net>
Cc: Denys <denys@visp.net.lb>, netdev@vger.kernel.org
Subject: Re: [re] Possible 2.6.22 -> 2.6.23 HTB regression?
Date: Wed, 10 Oct 2007 09:12:43 -0400 [thread overview]
Message-ID: <1192021963.4853.21.camel@localhost> (raw)
In-Reply-To: <470CC97F.4000906@trash.net>
On Wed, 2007-10-10 at 14:45 +0200, Patrick McHardy wrote:
> OK, hrtimers are disabled on your system, but we still announce
> the usec clock resolution to userspace, which is used by HTB to
> calculate the burst rate. But actually that can't be the reason
> since that has already been the case in 2.6.22. Please post a diff
> of the bootlog from 2.6.22 and 2.6.23.
Any possible relation to clock source? logs seem to indicate acpi
source; how does tsc or jiffies do?
BTW, I could be wrong about this, but iirc in a xeon i had access to i
saw that i could not guarantee the same clock source would be selected
across reboots in about 2.6.22.
cheers,
jamal
next prev parent reply other threads:[~2007-10-10 13:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 12:45 [re] Possible 2.6.22 -> 2.6.23 HTB regression? Denys
2007-10-10 12:45 ` Patrick McHardy
2007-10-10 13:12 ` jamal [this message]
2007-10-10 13:31 ` Denys
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=1192021963.4853.21.camel@localhost \
--to=hadi@cyberus.ca \
--cc=denys@visp.net.lb \
--cc=kaber@trash.net \
--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 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.