From: Patrick McHardy <kaber@trash.net>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: Jesper Dangaard Brouer <jdb@comx.dk>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/2]: [NET_SCHED]: Making rate table lookups more flexible.
Date: Sun, 02 Sep 2007 23:16:54 +0200 [thread overview]
Message-ID: <46DB2846.2030400@trash.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0709022006380.20071@ask.diku.dk>
Jesper Dangaard Brouer wrote:
> On Sun, 2 Sep 2007, Patrick McHardy wrote:
>>
>>> This is not a ATM/ADSL only patch. This patch simply adds more
>>> flexibility to the rate tables. Afterwards we can start the discussion
>>> about how to use this new flexibility in tc/iproute2.
>>
>> I know, but that discussion should happen *before* merging any
>> changes to the kernel.
>
> Let not try to solve too many things at once. We need to do this in
> small steps. Please, lets not start long and borrowing discussion
> again, where we try to solve too many things at once.
We don't need many, but we do need *one* thing that actually
uses this and isn't controversial before merging.
>
>
>> Its pointless to add functionality that
>> won't be used afterwards or may need to be done differently.
>
> I believe that the functionality _will_ be used, also in the general
> case.
>
> Lets focus on the general case, where the functionality actually is
> needed right away.
>
> In the general case:
>
> - The rate table needs to be aligned (cell_align=-1).
> (currently, we miscalculates up to 7 bytes on every lookup)
We will always do that, thats a consequence of storing the
transmission times for multiples of 8b.
>
> - The existing tc overhead calc can be made more accurate.
> (by adding overhead before doing the lookup, instead of the
> current solution where the rate table is modified with its
> limited resolution)
Please demonstrate this with patches (one for the overhead
calculation, one for the cell_align thing), then we can
continue this discussion.
>
>
> Patrick, note that your STAB solution will _not_ work without the rate
> table alignment.
I can't argue about this without looking into it again first,
but it shouldn't really matter for now since we don't have
a patch to actually implement it.
next prev parent reply other threads:[~2007-09-02 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 12:22 [PATCH 2/2]: [NET_SCHED]: Making rate table lookups more flexible Jesper Dangaard Brouer
2007-09-01 7:10 ` Patrick McHardy
2007-09-01 21:56 ` Jesper Dangaard Brouer
2007-09-02 14:35 ` Patrick McHardy
2007-09-02 18:56 ` Jesper Dangaard Brouer
2007-09-02 21:16 ` Patrick McHardy [this message]
2007-09-03 14:19 ` Jesper Dangaard Brouer
2007-09-04 16:25 ` Patrick McHardy
2007-09-05 13:58 ` Jesper Dangaard Brouer
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=46DB2846.2030400@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=hawk@diku.dk \
--cc=jdb@comx.dk \
--cc=netdev@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.