netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [RFC] sched: CHOKe packet scheduler (v0.4)
Date: Tue, 11 Jan 2011 15:48:06 -0800	[thread overview]
Message-ID: <20110111154806.6525e210@s6510> (raw)
In-Reply-To: <1294727650.4148.20.camel@edumazet-laptop>

On Tue, 11 Jan 2011 07:34:10 +0100
Eric Dumazet <eric.dumazet@gmail.com> wrote:

> Le mardi 11 janvier 2011 à 07:18 +0100, Eric Dumazet a écrit :
> > Le lundi 10 janvier 2011 à 17:10 -0800, Stephen Hemminger a écrit :
> > > OK, put that in.
> > 
> > Thanks !
> > 
> > > > 
> > > > Here we missed :
> > > > 
> > > > 		q->tab = ntab;
> > > > 
> > 
> > We also need to change 
> > 
> > .peek       =   qdisc_peek_head,
> > 
> > to
> > 
> > .peek = choke_peek_head,
> > 
> > static struct sk_buff *choke_peek_head(struct Qdisc *sch)
> > {
> > 	struct choke_sched_data *q = qdisc_priv(sch);
> > 
> > 	return (q->head != q->tail) ? q->tab[q->head] : NULL;
> > }
> > 
> > 
> 
> 
> And to correctly work with CBQ (at least...), we need to update 
> sch->q.qlen = choke_len(q) - q->holes;
> in dequeue() and enqueue()
> 
> Here is the version I successfully tested, with 30000 packets in
> queue :)
> 
> qdisc choke 11: parent 1:11 limit 70000b min 10000b max 30000b ewma 1 Plog 16 Scell_log 11
>  Sent 62099201 bytes 112920 pkt (dropped 367712, overlimits 282668 requeues 0) 
>  rate 21344Kbit 4851pps backlog 39877589b 30001p requeues 0 
>   marked 0 early 282668 pdrop 0 other 0

Maybe we should take over one of the red counters for the probabilistic match drop.


  reply	other threads:[~2011-01-11 23:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05  0:29 [RFC] sched: CHOKe packet scheduler Stephen Hemminger
2011-01-05  6:02 ` Eric Dumazet
2011-01-05  6:19 ` Eric Dumazet
2011-01-05 17:17   ` Stephen Hemminger
2011-01-05 17:25     ` Eric Dumazet
2011-01-05 19:21       ` [RFC] sched: CHOKe packet scheduler (v0.2) Stephen Hemminger
2011-01-05 20:06         ` Eric Dumazet
2011-01-05 20:15           ` Stephen Hemminger
2011-01-06  4:07         ` Eric Dumazet
2011-01-06  6:53           ` Stephen Hemminger
2011-01-07  4:55           ` Stephen Hemminger
2011-01-07  5:39             ` Changli Gao
2011-01-07  7:10               ` Stephen Hemminger
2011-01-07  8:37             ` Eric Dumazet
2011-01-10 13:46             ` Eric Dumazet
2011-01-10 17:31               ` Stephen Hemminger
2011-01-10 17:45                 ` Eric Dumazet
2011-01-10 23:44               ` [RFC] sched: CHOKe packet scheduler (v0.4) Stephen Hemminger
2011-01-11  0:00                 ` Eric Dumazet
2011-01-11  1:10                   ` Stephen Hemminger
2011-01-11  6:18                     ` Eric Dumazet
2011-01-11  6:34                       ` Eric Dumazet
2011-01-11 23:48                         ` Stephen Hemminger [this message]
2011-01-12  0:04                           ` Eric Dumazet
2011-01-12  7:13                         ` [RFC] sched: CHOKe packet scheduler (v0.6) Eric Dumazet
2011-01-12 17:27                           ` Stephen Hemminger
2011-01-12 17:33                             ` Eric Dumazet

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=20110111154806.6525e210@s6510 \
    --to=shemminger@vyatta.com \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).