All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] patch: HTB update for ADSL users
Date: Tue, 22 Jun 2004 09:54:32 +0000	[thread overview]
Message-ID: <40D801D8.4000006@wildgooses.com> (raw)
In-Reply-To: <40D2D5CB.2000804@wildgooses.com>

Damion de Soto wrote:

>> After further investigation I think you need the patch a little more 
>> like this for PPPoE and the params you gave (Andy do you think this 
>> looks OK?)  Please let me know if this works for you.
>>
>> (As near as I can tell, there is no PPP overhead(?), and you then 
>> basically encapsulate your packets in IP packets of max size 1492, 
>> with an 8 byte overhead - Perhaps Andy can correct me as to whether 
>> there is still a PPP overhead?)
>
> I wonder if there's any easy way we can get the ATM/PPPoE support enabled
> at runtime.


Yeah, I was thinking of adding a module param in the final version, 
something like "encaps PPPoA" or similar

> I guess a tc option would be needed to enable ADSL (atm) numbers,
> but the HTB qdisc should be able to detect PPP packets for PPPoE, right ?
> at least egress on any pppX interface.


Now that's a very interesting question.  The size is passed in as the 
size of the packet that the kernel sees (including headers).  We mangle 
that to get the size sent over the ATM link.  However, I have ethernet 
on both sides in my setup.  I wonder what the kernel sees if one 
interface is PPP?  Is it already encapsulated in PPP before QOS gets it, 
or not?

> Are you using this patch just for inbound shaping on pppX, or does it 
> still make sense to use it on an IMQ device, or on a LAN-side ethX 
> device to do the equivalent of ingress shaping ?


Use it for both.

Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-06-22  9:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 11:45 [LARTC] patch: HTB update for ADSL users Ed Wildgoose
2004-06-18 21:43 ` Andy Furniss
2004-06-18 23:00 ` Ed Wildgoose
2004-06-19  0:33 ` Andy Furniss
2004-06-19 12:29 ` Ed Wildgoose
2004-06-19 12:54 ` syrius.ml
2004-06-19 13:40 ` Ed Wildgoose
2004-06-20  7:27 ` Jason Boxman
2004-06-20 12:31 ` Andy Furniss
2004-06-20 13:16 ` Ed Wildgoose
2004-06-20 16:46 ` Ed Wildgoose
2004-06-20 17:10 ` Ed Wildgoose
2004-06-21  6:08 ` Jason Boxman
2004-06-21 10:04 ` Ed Wildgoose
2004-06-22  0:38 ` Damion de Soto
2004-06-22  5:15 ` Jason Boxman
2004-06-22  9:54 ` Ed Wildgoose [this message]
2004-06-22 10:00 ` Ed Wildgoose
2004-06-22 17:16 ` Jason Boxman
2004-06-22 21:52 ` Jason Boxman
2004-06-23 12:52 ` ThE LinuX_KiD
2004-06-23 14:00 ` Ed Wildgoose

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=40D801D8.4000006@wildgooses.com \
    --to=lists@wildgooses.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.