All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Atanasov <alex@ssi.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] SFQ buckets/extensions
Date: Fri, 07 Jun 2002 08:26:14 +0000	[thread overview]
Message-ID: <marc-lartc-102343845812347@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102329319618482@msgid-missing>

On Thu, 6 Jun 2002, Don Cohen wrote:

> Maybe you think it's just incredibly lucky that these sources are
> both sending at just the same rate that they're being served, but
> that's what tcp is supposed to do.  

	No, i do not think like this. If we think just for TCP connections
we may end up with ideas like changig window size. TCP tunes to send this
way but it also tries to send more each 5 seconds, if it have data.
SFQ classify connections with ports, esfq classify them and just by IP so
we can have flows:
	SRC IP+proto+DST IP+PORT - one flow
	just DST IP - one flow
	another	we can think of - one flow
So i think just about packets of size bytes but without protos which they
carry and TCP with its features to tune becomes a kind of exception.

> 
>  > Measurement in bytes can make this more incorrect since you have enqueued
>  > packets with different lenghts which you can not split a part and dequeue
>  > in bytes (sigh wouldn't it be nice? ), counting queues in packets (exactly
>  > what they have) is better. May be doing it like the cbq with average
>  > packet size can gave us better results.
> No, the errors are accumulated.  It's always within one packet of the
> ideal in terms of what's sent.  The advantage of measuring queue
> length in bytes would be more fairness in dropping, i.e., you should
> drop from a queue with 10 packets each of length 1000 bytes instead of
> a queue with 20 packets each of length 100 bytes.

	I didn't get it ? What do you mean - have different queues 
agains packets sizes ?

> I think the version I sent does give control over queue size and
> number of buckets.  It also gives you something called expire, which
> I think might do the same sort of thing that you wanted from your
> limits.  We've discussed it on this list before so I won't go into it
> again. 

	We need a way to control what happens in a subqueue there
are these for now:
	- Time limits you've implemented
	- Someone asked about (G)RED
	- devik asked about wrr for connections
	- others ?

-- 
have fun,
alex

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

  parent reply	other threads:[~2002-06-07  8:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-05 16:04 [LARTC] SFQ buckets/extensions Don Cohen
2002-06-06  0:53 ` Alexander Atanasov
2002-06-06  6:01 ` Don Cohen
2002-06-06 13:05 ` Michael T. Babcock
2002-06-06 23:06 ` Alexander Atanasov
2002-06-06 23:38 ` Don Cohen
2002-06-07  1:33 ` Alexander Atanasov
2002-06-07  1:59 ` Don Cohen
2002-06-07  8:26 ` Alexander Atanasov [this message]
2002-06-07 14:18 ` Michael T. Babcock
2002-06-07 14:37 ` Jan Coppens
2002-06-07 16:14 ` Don Cohen
2002-06-07 18:13 ` Martin Devera
2002-06-07 18:38 ` Martin Devera
2002-06-07 19:01 ` Michael T. Babcock
2002-06-07 19:08 ` Martin Devera
2002-06-07 19:50 ` Michael T. Babcock
2002-06-08 18:42 ` Gregory Maxwell

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-102343845812347@msgid-missing \
    --to=alex@ssi.bg \
    --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.