* [re] Possible 2.6.22 -> 2.6.23 HTB regression?
@ 2007-10-10 12:45 Denys
2007-10-10 12:45 ` Patrick McHardy
0 siblings, 1 reply; 4+ messages in thread
From: Denys @ 2007-10-10 12:45 UTC (permalink / raw)
To: netdev; +Cc: kaber
> What does /proc/net/psched contain?
visp-1 ~ # cat /proc/net/psched
000003e8 00000400 000f4240 3b9aca00
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [re] Possible 2.6.22 -> 2.6.23 HTB regression?
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
0 siblings, 1 reply; 4+ messages in thread
From: Patrick McHardy @ 2007-10-10 12:45 UTC (permalink / raw)
To: Denys; +Cc: netdev
Denys wrote:
>>What does /proc/net/psched contain?
>
> visp-1 ~ # cat /proc/net/psched
> 000003e8 00000400 000f4240 3b9aca00
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [re] Possible 2.6.22 -> 2.6.23 HTB regression?
2007-10-10 12:45 ` Patrick McHardy
@ 2007-10-10 13:12 ` jamal
2007-10-10 13:31 ` Denys
0 siblings, 1 reply; 4+ messages in thread
From: jamal @ 2007-10-10 13:12 UTC (permalink / raw)
To: Patrick McHardy; +Cc: Denys, netdev
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [re] Possible 2.6.22 -> 2.6.23 HTB regression?
2007-10-10 13:12 ` jamal
@ 2007-10-10 13:31 ` Denys
0 siblings, 0 replies; 4+ messages in thread
From: Denys @ 2007-10-10 13:31 UTC (permalink / raw)
To: hadi, Patrick McHardy; +Cc: netdev
Patch applied. Rebooted over kexec to 2.6.23 without nmi_watchdog, for now
all seems fine.
visp-1 ~ # cat /proc/net/psched
000003e8 00000400 000f4240 3b9aca00
82942/82949 KBit/S (53083445/53087945) (106109614/106105114)
82955/82955 KBit/S (53091631/53091631) (159193059/159193059)
82955/82955 KBit/S (53091351/53091351) (212284690/212284690)
82951/82951 KBit/S (53088902/53088902) (265376041/265376041)
82940/82940 KBit/S (53081605/53081605) (318464943/318464943)
82959/82959 KBit/S (53094269/53094269) (371546548/371546548)
81596/81596 KBit/S (52221918/52221918) (424640817/424640817)
82909/82909 KBit/S (53062055/53062055) (476862735/476862735)
82939/82939 KBit/S (53081402/53081402) (529924790/529924790)
82963/82963 KBit/S (53096554/53096554) (583006192/583006192)
82954/82954 KBit/S (53090871/53090871) (636102746/636102746)
82030/82943 KBit/S (52499816/53084066) (689193617/689193617)
82945/82945 KBit/S (53085182/53085182) (741693433/742277683)
82964/82954 KBit/S (53097002/53091002) (794778615/795362865)
--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-10-10 13:42 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2007-10-10 13:31 ` Denys
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).