From: devik <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB not that exact
Date: Sat, 08 Dec 2001 15:18:48 +0000 [thread overview]
Message-ID: <marc-lartc-100782716913818@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100766696815760@msgid-missing>
> > > -#define PSCHED_CLOCK_SOURCE PSCHED_JIFFIES
> > > +#define PSCHED_CLOCK_SOURCE PSCHED_CPU
> >
> > by the way if you have pentium with tsc the patch above
> > is stronly recommended. It allows for sub nanosecond
> > precision...
> > devik
>
> Is there a reason not to do this? In which case we should probably submit a
> patch that makes PSCHED_CPU the default if you have a TSC.
It would be nice - but when ANK does somethink in some way
there is reason usualy.
I've already been thinking about it as
#ifdef CONFIG_X86_TSC
#define PSCHED_CLOCK_SOURCE PSCHED_CPU
....
I can found no reason why don't use TSC. With highly loaded
interface where eth interrupts are faster than timer ones
it should make flow smoother.
Without TSC all packets within single timer tick (10ms) are
treated as havin the same arival time.
CBQ's clock integrator based on HW speed computations overcomes
this and it might be reason why ANK left JIFFIES here.
If you think that you have such power to convince people
about it then go ahead. :)
devik
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-12-08 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 19:28 [LARTC] HTB not that exact Stefan Rompf
2001-12-06 19:48 ` bert hubert
2001-12-06 20:33 ` Daniel Ryczek
2001-12-06 21:35 ` Stefan Rompf
2001-12-07 11:46 ` david
2001-12-07 16:57 ` Sami Farin
2001-12-08 8:51 ` Martin Devera
2001-12-08 11:52 ` bert hubert
2001-12-08 11:53 ` bert hubert
2001-12-08 15:18 ` devik [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-100782716913818@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 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.