All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How far can TC go?
Date: Sat, 29 Mar 2003 10:08:30 +0000	[thread overview]
Message-ID: <marc-lartc-104893259213112@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104891452701060@msgid-missing>

Randolph Carter wrote:

>I have been working with HTB for around 10months; I've been testing it on
>several enviroments and have had a good experience with. I'm Wondering if
>if I could use HTB in a more agressive environment; and use some
>feautures like layer-5-7 recogniction in order to bring a clever shaping.
>
>Does somebody know if traffic control suplied by Linux could be compared
>to the DTS supplied by CISCO; or if we can aim to do a job as dyband or
>packeteer do?
>
>Which are the limitations to our shaping system? Can we build a real
>commercial solution?
>  
>

Packeteer has various patents covering tcp rate control and everything else
they do, including the "idea" to look at upper layers to detect the type 
of traffic.
I live in germany so i don't really care that much about their patents 
(they had none
in europe last time i checked). last summer i started implementing tcp 
rate control
as qdisc for linux. i haven't worked on it for a couple of month now, 
but if anyone wishes
to participate i would be glad to dig out my source again. it is 
basically working, the
remaining problems are mostly how to detect and handle interactive traffic.

Patrick

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

  reply	other threads:[~2003-03-29 10:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-29  5:07 [LARTC] How far can TC go? Randolph Carter
2003-03-29 10:08 ` Patrick McHardy [this message]
2003-03-29 15:19 ` Randolph Carter

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=marc-lartc-104893259213112@msgid-missing \
    --to=kaber@trash.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.