From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [Bulk] Re: [LARTC] has anyone tried adsl-optmizer kernel patches
Date: Thu, 24 Nov 2005 15:13:18 +0000 [thread overview]
Message-ID: <4385D88E.6080307@dsl.pipex.com> (raw)
In-Reply-To: <43846D68.2050709@yahoo.fr>
Sophana Kok wrote:
> Markus Schulz wrote:
>
>> On Wednesday 16 November 2005 16:03, Andy Furniss wrote:
>>
>>
>>> I use something similar and use ceil 286kbit while synced at 288kbit
>>> without problems.
>>>
>
> What thing similar do you use? I don't understand why it is not in the
> kernel already.
I use my own based on the tc tweak that Ed Wildgoose posted to the list,
but patching htb aswell so it's perfect (the tc alone patch is a cell
too big for some packet sizes)
>
>> should be easy to patch in. Overhead is only a simple variable which
>> will be added in htb/* module for each paket. Only sign/unsign
>> problem should be considered.
>>
>>
> How?
>
> The ppp over aal5 atm encapsulation is in almost all adsl lines isn't it?
> Isn't it standard?
In jeesper's thesis there is a table - Knowing you overhead can be
tricky - but you can test, best if your modem gives cell counters or
even if it doesn't on adsl you may be able to see differences in
throughput/latency if you look hard enough.
> This makes a huge number of lines in the world.
> Are there other patches ?
> or distributions that already include these patches?
I don't think so, patching is easy you need to test and know your
overheads aswell.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-11-24 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 13:23 [Bulk] Re: [LARTC] has anyone tried adsl-optmizer kernel patches Sophana Kok
2005-11-23 16:11 ` Markus Schulz
2005-11-24 15:13 ` Andy Furniss [this message]
2005-11-24 15:33 ` Andy Furniss
2005-11-24 21:35 ` sophana
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=4385D88E.6080307@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--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.