All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH iproute2] fq_codel: add per queue memory limit
Date: Wed, 8 Jun 2016 08:33:20 -0700	[thread overview]
Message-ID: <20160608083320.7d950b9a@xeon-e3> (raw)
In-Reply-To: <1464791011.5939.150.camel@edumazet-glaptop3.roam.corp.google.com>

On Wed, 01 Jun 2016 07:23:31 -0700
Eric Dumazet <eric.dumazet@gmail.com> wrote:

> From: Eric Dumazet <edumazet@google.com>
> 
> This patch adds support for TCA_FQ_CODEL_MEMORY_LIMIT attribute.
> 
> # tc qd replace dev eth1 root est 1sec 4sec fq_codel memory_limit 4M
> ..
> # tc -s -d qd sh dev eth1
> qdisc fq_codel 8008: root refcnt 257 limit 10240p flows 1024
>  quantum 1514 target 5.0ms interval 100.0ms memory_limit 4Mb ecn
>  Sent 2083566791363 bytes 1376214889 pkt (dropped 4994406, overlimits 0
> requeues 21705223)
>  rate 9841Mbit 812549pps backlog 3906120b 376p requeues 21705223
>   maxpacket 68130 drop_overlimit 4994406 new_flow_count 28855414
>   ecn_mark 0 memory_used 4190048 drop_overmemory 4994406
> new_flows_len 1 old_flows_len 177
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>

Applied but I had to fix a couple of conflicts because recent checkpatch cleanup
of tc files.

  parent reply	other threads:[~2016-06-08 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-01 14:23 [PATCH iproute2] fq_codel: add per queue memory limit Eric Dumazet
2016-06-01 15:53 ` Stephen Hemminger
2016-06-01 16:01   ` Eric Dumazet
2016-06-08 15:33 ` Stephen Hemminger [this message]
2016-06-08 22:28   ` 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=20160608083320.7d950b9a@xeon-e3 \
    --to=stephen@networkplumber.org \
    --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 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.