All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Theory test
Date: Tue, 06 Dec 2005 16:11:15 +0000	[thread overview]
Message-ID: <4395B823.8010205@dsl.pipex.com> (raw)
In-Reply-To: <fad9d4840512050942h5a9e63cbv431cbfa890fa3831@mail.gmail.com>

Kenneth Kalmer wrote:

> ADSL, 512kbps down and 256kbps up. Parent for the internet traffic is
> set at 500kbps, to make sure it becomes the bottleneck...

I used to use 400 when I had 512 ingress, so I am amazed that works - 
but then you say ingress not the problem.

> I attach an esfq to each child HTB, but as you say it would be less
> relevenat for egress...

Were it ingress I woud say have just one class with esfq for sharing out 
bulk traffic per user.

>>Do you know what type of connection you have eg pppoa/e or bridged ip
>>etc. I assume whatever it is ends up as atm cells?
> 
> Barely, as said above it's 512/256 VPN. Underneath the VPN it runs
> PPPoE, but the service simulates a leased line, static ip's, the
> works...

I bet there are alot of overheads on that - and if you are pushing the 
rate close to limit like you are on ingress I suspect you are going 
overlimits. Even if you test with an upload and find a rate that seems 
OK it will all fall apart when the traffic consists of small packets.

You have real ips aswell - so all your students can become p2p nodes = 
lots of small packets. I would consider using htb's mpu and overhead on 
each rate/ceil mpu with pppoe/atm is going to be 106 bytes - overhead I 
am not sure as it's not normal dsl - if it were you could patch tc/htb 
to do it perfectly. Often your atm level sync rate will be a bit higher 
than the advertised rate. If you can get your kit to tell you what that 
is it will be helpful.

Andy.

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-12-06 16:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-05 17:42 [LARTC] Theory test Kenneth Kalmer
2005-12-05 18:03 ` Peter Surda
2005-12-05 18:06 ` Andreas Klauer
2005-12-05 19:59 ` Andy Furniss
2005-12-05 22:57 ` Kenneth Kalmer
2005-12-05 23:01 ` Kenneth Kalmer
2005-12-05 23:03 ` Kenneth Kalmer
2005-12-06  1:18 ` Andy Furniss
2005-12-06 13:48 ` Kenneth Kalmer
2005-12-06 16:11 ` Andy Furniss [this message]
2005-12-06 18:50 ` Kenneth Kalmer
2005-12-06 20:07 ` Andy Furniss
2005-12-06 21:52 ` Kenneth Kalmer
2005-12-06 22:17 ` Kenneth Kalmer

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=4395B823.8010205@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.