From: Jiri Pirko <jiri@resnulli.us>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
jhs@mojatatu.com, kuznet@ms2.inr.ac.ru, j.vimal@gmail.com
Subject: Re: [patch net-next v2 10/11] act_police: improved accuracy at high rates
Date: Fri, 8 Feb 2013 23:16:08 +0100 [thread overview]
Message-ID: <20130208221608.GA1516@minipsycho.orion> (raw)
In-Reply-To: <1360350755.28557.108.camel@edumazet-glaptop>
Fri, Feb 08, 2013 at 08:12:35PM CET, eric.dumazet@gmail.com wrote:
>On Fri, 2013-02-08 at 19:59 +0100, Jiri Pirko wrote:
>> Current act_police uses rate table computed by the "tc" userspace program,
>> which has the following issue:
>>
>> The rate table has 256 entries to map packet lengths to
>> token (time units). With TSO sized packets, the 256 entry granularity
>> leads to loss/gain of rate, making the token bucket inaccurate.
>>
>> Thus, instead of relying on rate table, this patch explicitly computes
>> the time and accounts for packet transmission times with nanosecond
>> granularity.
>>
>> This is a followup to 56b765b79e9a78dc7d3f8850ba5e5567205a3ecd
>>
>> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
>> ---
>> net/sched/act_police.c | 119 +++++++++++++++++++++++--------------------------
>> 1 file changed, 57 insertions(+), 62 deletions(-)
>>
>> diff --git a/net/sched/act_police.c b/net/sched/act_police.c
>> index 378a649..8723183 100644
>> --- a/net/sched/act_police.c
>> +++ b/net/sched/act_police.c
>> @@ -26,20 +26,19 @@ struct tcf_police {
>> struct tcf_common common;
>> int tcfp_result;
>> u32 tcfp_ewma_rate;
>> - u32 tcfp_burst;
>> + s64 tcfp_burst;
>> u32 tcfp_mtu;
>> - u32 tcfp_toks;
>> - u32 tcfp_ptoks;
>> + s64 tcfp_toks;
>> + s64 tcfp_ptoks;
>> psched_time_t tcfp_t_c;
>> - struct qdisc_rate_table *tcfp_R_tab;
>> - struct qdisc_rate_table *tcfp_P_tab;
>> + struct psched_ratecfg rate;
>> + bool rate_present;
>> + struct psched_ratecfg peak;
>> + bool peak_present;
>> };
>> #define to_police(pc) \
>> container_of(pc, struct tcf_police, common)
>>
>> -#define L2T(p, L) qdisc_l2t((p)->tcfp_R_tab, L)
>> -#define L2T_P(p, L) qdisc_l2t((p)->tcfp_P_tab, L)
>> -
>> #define POL_TAB_MASK 15
>> static struct tcf_common *tcf_police_ht[POL_TAB_MASK + 1];
>> static u32 police_idx_gen;
>> @@ -123,10 +122,6 @@ static void tcf_police_destroy(struct tcf_police *p)
>> write_unlock_bh(&police_lock);
>> gen_kill_estimator(&p->tcf_bstats,
>> &p->tcf_rate_est);
>> - if (p->tcfp_R_tab)
>> - qdisc_put_rtab(p->tcfp_R_tab);
>> - if (p->tcfp_P_tab)
>> - qdisc_put_rtab(p->tcfp_P_tab);
>> /*
>> * gen_estimator est_timer() might access p->tcf_lock
>> * or bstats, wait a RCU grace period before freeing p
>> @@ -154,7 +149,6 @@ static int tcf_act_police_locate(struct net *net, struct nlattr *nla,
>> struct nlattr *tb[TCA_POLICE_MAX + 1];
>> struct tc_police *parm;
>> struct tcf_police *police;
>> - struct qdisc_rate_table *R_tab = NULL, *P_tab = NULL;
>> int size;
>>
>> if (nla == NULL)
>> @@ -197,21 +191,37 @@ static int tcf_act_police_locate(struct net *net, struct nlattr *nla,
>> if (bind)
>> police->tcf_bindcnt = 1;
>> override:
>> + spin_lock_bh(&police->tcf_lock);
>> + police->tcfp_mtu = parm->mtu;
>> + police->rate_present = false;
>> + police->peak_present = false;
>> if (parm->rate.rate) {
>> + struct qdisc_rate_table *tab;
>> +
>> err = -ENOMEM;
>> - R_tab = qdisc_get_rtab(&parm->rate, tb[TCA_POLICE_RATE]);
>> - if (R_tab == NULL)
>> - goto failure;
>> + tab = qdisc_get_rtab(&parm->rate, tb[TCA_POLICE_RATE]);
>
>This patch was not tested, it cannot possibly work
>
>spin_lock_bh();
>rtab = kmalloc(sizeof(*rtab), GFP_KERNEL);
>
>should crash or complain loudly.
Thanks, you are right, I had this debug option disabled. Will repost.
>
>
next prev parent reply other threads:[~2013-02-08 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-08 18:59 [patch net-next v2 00/11] couple of net/sched fixes+improvements Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 01/11] htb: use PSCHED_TICKS2NS() Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 02/11] htb: fix values in opt dump Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 03/11] htb: remove pointless first initialization of buffer and cbuffer Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 04/11] htb: initialize cl->tokens and cl->ctokens correctly Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 05/11] sch: make htb_rate_cfg and functions around that generic Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 06/11] tbf: improved accuracy at high rates Jiri Pirko
2013-02-08 19:09 ` Eric Dumazet
2013-02-08 18:59 ` [patch net-next v2 07/11] tbf: ignore max_size check for gso skbs Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 08/11] tbf: fix value set for q->ptokens Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 09/11] act_police: move struct tcf_police to act_police.c Jiri Pirko
2013-02-08 18:59 ` [patch net-next v2 10/11] act_police: improved accuracy at high rates Jiri Pirko
2013-02-08 19:12 ` Eric Dumazet
2013-02-08 22:16 ` Jiri Pirko [this message]
2013-02-08 18:59 ` [patch net-next v2 11/11] act_police: remove <=mtu check for gso skbs Jiri Pirko
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=20130208221608.GA1516@minipsycho.orion \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=j.vimal@gmail.com \
--cc=jhs@mojatatu.com \
--cc=kuznet@ms2.inr.ac.ru \
--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