From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2005@gmx.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] New HTB-derived qdisc for accounting?
Date: Sat, 04 Jun 2005 18:46:17 +0000 [thread overview]
Message-ID: <42A1F6F9.1080602@gmx.net> (raw)
In-Reply-To: <42A1A26A.1010700@gmx.net>
Patrick McHardy schrieb:
> Carl-Daniel Hailfinger wrote:
>
>>Proposal:
>>----------------------------------
>>Another idea would be to create a qdisc HTBQ (HTB with quota)
>>derived from HTB with the following characteristics:
>>
>>htb_rate=min(htbq_rate, (alreadysent=>htbq_squota)?((htbq_quota-alreadysent)/remtime):htbq_rate)
>
>
> Why do you want to decrease speed as the quota is approached?
We have two phases (simplified):
1. Already sent traffic is less than htbq_squota
-> Do not limit anything.
2. Already sent traffic is more than htbq_squota
-> Limit the rate to something which allows the quota
to be filled completely in the remainig time.
Most people stay below htbq_squota and do not notice
anything at all, i.e. they get full wire speed. Power users
will cause more traffic than htb_squota and be limited so
they can't get over htbq_quota. Since it is impossible to
send faster than htb_rate, htb_rate will stay constant if
it is fully utilized. If htb_rate is not fully utilized,
the speed will actually *increase* over time.
> Wouldn't a simple per-class quota or a quota-ematch work as
> well?
That would be easier, but I can't see how to realize the
process above with a quota-ematch. Especially the dynamic
rate adaption needs something more than just quota.
Probably one could combine quota-ematch with some userspace
hackery to achieve what I want, but it would require to
statically set up 65536 classes for a /16 network. Hm.
The only difference to my solution would be that we need
a quota ematch instead of a htb_quota qdisc and rate control
would be done in userspace.
So where can I find code doing a quota ematch?
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-06-04 18:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 12:45 [LARTC] New HTB-derived qdisc for accounting? Carl-Daniel Hailfinger
2005-06-04 12:54 ` Peter Surda
2005-06-04 13:21 ` Carl-Daniel Hailfinger
2005-06-04 13:35 ` Patrick McHardy
2005-06-04 13:39 ` Peter Surda
2005-06-04 18:46 ` Carl-Daniel Hailfinger [this message]
2005-06-06 14:02 ` Patrick McHardy
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=42A1F6F9.1080602@gmx.net \
--to=c-d.hailfinger.devel.2005@gmx.net \
--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.