All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH -next] net: sched: use counter to break reclassify loops
Date: Wed, 13 May 2015 08:04:27 -0400	[thread overview]
Message-ID: <55533DCB.2070703@mojatatu.com> (raw)
In-Reply-To: <20150513112958.GA6179@breakpoint.cc>

On 05/13/15 07:29, Florian Westphal wrote:
> Jamal Hadi Salim <jhs@mojatatu.com> wrote:

> Yes, but, if we use your example above then:
>
> tc_classify called
>    limit 0
>      tc_classify_compat called, ret RECLASSIFY
>    limit 1
>      tc_classify_compat called, ret RECLASSIFY
>    limit 2
>      tc_classify_compat called, ret PIPE (== 3)
>    tc_classify returns 3
> tc_classify called
>    limit 0
>    ...
>
> So we don't toss skb since any return value other than RECLASSIFY
> will make tc_classify() return to its caller, and when caller invokes
> tc_classify again the limit variable is set to 0 again.
>
> Does that make sense to you?
>

I think you are right.

I am probably conflating the inner action loop execution with this
outer one. I will think some more about it and if i can come up with
other scenario.
In any case, lets not slow this down; please add my acked-by and if
i can think of something i will post. I have to take off, so i will go
quiet for a while.

cheers,
jamal

  reply	other threads:[~2015-05-13 12:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-11 17:50 [PATCH -next] net: sched: use counter to break reclassify loops Florian Westphal
2015-05-11 20:30 ` Alexei Starovoitov
2015-05-12 11:38 ` Jamal Hadi Salim
2015-05-12 13:00   ` Florian Westphal
2015-05-13 11:18     ` Jamal Hadi Salim
2015-05-13 11:29       ` Florian Westphal
2015-05-13 12:04         ` Jamal Hadi Salim [this message]
2015-05-13 12:44           ` Florian Westphal
2015-05-13 19:08 ` David Miller

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=55533DCB.2070703@mojatatu.com \
    --to=jhs@mojatatu.com \
    --cc=fw@strlen.de \
    --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.