From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] About HTB3
Date: Mon, 24 Jun 2002 07:52:33 +0000 [thread overview]
Message-ID: <marc-lartc-102490527320738@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102454870301498@msgid-missing>
Exactly :) Alphas used to set 1024 as default. It is because
Alpha was very low interrupt latency compared to x86.
On Mon, 24 Jun 2002, Amit Kucheria wrote:
> IMHO :)
>
> HZ defines the heart beat of the Linux system in terms of 'jiffies'.
> Increasing HZ will increase the number of interrupts on the system (e.g.
> timer interrupt) and hence might not be useful for typical desktops, since
> handling these system interrupts will not leave much CPU time for
> applications.
>
> But for a server which usually does only one thing (e.g. enforcing QoS),
> this increase in the interrupts should not be a problem.
>
> I configure my servers with HZ\x1024 regularly in include/net/pkt_sched.h
> without any problems.
>
> ciao,
> Amit
>
> On Mon, 24 Jun 2002, Martin Devera wrote:
>
> > I change it regulary. I didn't experienced any problems - only
> > lockups on slow systems which can't handle it.
> > There should be no problem regarding the change.
> > devik
> >
> > On Mon, 24 Jun 2002, Alexey Talikov wrote:
> >
> > > I can't answer you completely ( this question for kernel maintainers ) :(
> > > But as I know this value used for IRQ (see arch/i386/kernel/irq.c)
> > > different kernel timers (arch/i386/kernel/time.c) for SMP (multiprocessor)
> > > in APIC functions ASPI functions almost in all drivers even in PCI bus
> > > and ATM subsystem and many many other
> > >
> > > I have no idea about after-effects of change HZ !
> > > I don't know about possibility to change this value only for traffic control functions !
> > >
> > > I think change this value for Ix86 architecture not so simple !
> > >
> > > If somebody have idea about this, share it with me !
> > >
>
> --
> I'm an angel!!! Honest!
> The horns are just there to hold the halo up straight.
> ^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^
> Amit Kucheria
> EECS Grad. Research Assistant
> University of Kansas @ Lawrence
> (R): +1-785-830-8521 ||| (C): +1-785-760-2871
> ____________________________________________________
>
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-06-24 7:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 4:53 [LARTC] About HTB3 yangrunhua
2002-06-20 5:45 ` Alexey Talikov
2002-06-23 9:39 ` bert hubert
2002-06-24 4:34 ` Alexey Talikov
2002-06-24 7:29 ` Martin Devera
2002-06-24 7:40 ` Amit Kucheria
2002-06-24 7:52 ` Martin Devera [this message]
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=marc-lartc-102490527320738@msgid-missing \
--to=devik@cdi.cz \
--cc=lartc@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