netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, ast@plumgrid.com, jhs@mojatatu.com,
	john.fastabend@gmail.com
Subject: Re: [PATCH net] net_sched: gen_estimator: extend pps limit
Date: Wed, 08 Jul 2015 13:59:56 -0700 (PDT)	[thread overview]
Message-ID: <20150708.135956.157230596810615593.davem@davemloft.net> (raw)
In-Reply-To: <1435845439.11970.25.camel@edumazet-glaptop2.roam.corp.google.com>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Thu, 02 Jul 2015 15:57:19 +0200

> From: Eric Dumazet <edumazet@google.com>
> 
> rate estimators are limited to 4 Mpps, which was fine years ago, but
> too small with current hardware generation.
> 
> Lets use 2^5 scaling instead of 2^10 to get 128 Mpps new limit.
> 
> On 64bit arch, use an "unsigned long" for temp storage and remove limit.
> (We do not expect 32bit arches to be able to reach this point)
> 
> Tested:
> 
> tc -s -d filter sh dev eth0 parent ffff:
> 
> filter protocol ip pref 1 u32 
> filter protocol ip pref 1 u32 fh 800: ht divisor 1 
> filter protocol ip pref 1 u32 fh 800::800 order 2048 key ht 800 bkt 0 flowid 1:15 
>   match 07000000/ff000000 at 12
> 	action order 1: gact action drop
> 	 random type none pass val 0
> 	 index 1 ref 1 bind 1 installed 166 sec
>  	Action statistics:
> 	Sent 39734251496 bytes 863788076 pkt (dropped 863788117, overlimits 0 requeues 0) 
> 	rate 4067Mbit 11053596pps backlog 0b 0p requeues 0 
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>

Applied, thanks.

      parent reply	other threads:[~2015-07-08 20:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 13:57 [PATCH net] net_sched: gen_estimator: extend pps limit Eric Dumazet
2015-07-02 17:15 ` Alexei Starovoitov
2015-07-08 20:59 ` David Miller [this message]

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=20150708.135956.157230596810615593.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=ast@plumgrid.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jhs@mojatatu.com \
    --cc=john.fastabend@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).