From: Dave Taht <dave.taht@gmail.com>
To: codel@lists.bufferbloat.net
Subject: [Codel] fp sqrt vis int sqrt?
Date: Fri, 4 May 2012 08:11:41 -0700 [thread overview]
Message-ID: <CAA93jw49KZZHBfb47cGN7tTxw8RbGzHHEVodhdpzmbOp78CREQ@mail.gmail.com> (raw)
The linux kernel has no floating point in it, so I'd substituted the
internal int_sqrt as a substitute,
just to get something to work.
static inline ktime_t control_law(const struct codel_sched_data *q, ktime_t t)
{
return ktime_add_ns(t, q->interval / int_sqrt(q->count));
}
Often ns2 models use floating point. Having not seen the model I don't
know that for sure.
The series for an integer sqrt is far more 'chunky' than a fp one.
int sqrt 1,2,3,4 = 1 1 1 2
fp sqrt 1 2 3 4 = 1 1.4.1 1.73 2
and gets even more chunky as you get larger values, eg, sqrt(36
through 48) = 6, sqrt(49) = 7
So we could precalculate the interval/sqrt(count) using floating point
in the control law calculation,
early, during qdisc setup, thus neatly avoiding both the divide and
sqrt in the control law path.
Or we could do fixed point.
Kathie: In the sim, in various simulations, what is the dynamic range
of count? And is it floating point sqrt?
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
next reply other threads:[~2012-05-04 15:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 15:11 Dave Taht [this message]
2012-05-04 15:14 ` Jim Gettys
2012-05-04 15:19 ` Dave Taht
2012-05-04 15:26 ` Jim Gettys
2012-05-04 15:56 ` Eric Dumazet
2012-05-04 17:23 ` Dave Taht
2012-05-04 17:43 ` Dave Taht
2012-05-04 17:44 ` Dave Taht
2012-05-04 17:46 ` Dave Taht
2012-05-04 23:42 ` Kathleen Nichols
2012-05-05 0:01 ` Dave Taht
2012-05-04 17:47 ` Eric Dumazet
2012-05-04 18:26 ` Eric Dumazet
2012-05-04 18:39 ` Dave Taht
2012-05-04 18:50 ` Eric Dumazet
2012-05-04 19:04 ` Dave Taht
2012-05-04 19:16 ` Eric Dumazet
2012-05-05 8:14 ` Eric Dumazet
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw49KZZHBfb47cGN7tTxw8RbGzHHEVodhdpzmbOp78CREQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=codel@lists.bufferbloat.net \
/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