All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Petr Machata <petrm@mellanox.com>, netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Jiri Pirko <jiri@mellanox.com>
Subject: Re: [PATCH iproute2-next v3 0/2] Support showing a block bound by qevent
Date: Mon, 20 Jul 2020 10:37:48 -0600	[thread overview]
Message-ID: <1a00088f-7d25-082c-422c-b3c16bc15f67@gmail.com> (raw)
In-Reply-To: <cover.1594917961.git.petrm@mellanox.com>

On 7/16/20 10:47 AM, Petr Machata wrote:
> When a list of filters at a given block is requested, tc first validates
> that the block exists before doing the filter query. Currently the
> validation routine checks ingress and egress blocks. But now that blocks
> can be bound to qevents as well, qevent blocks should be looked for as
> well:
> 
>     # ip link add up type dummy
>     # tc qdisc add dev dummy1 root handle 1: \
>          red min 30000 max 60000 avpkt 1000 qevent early_drop block 100
>     # tc filter add block 100 pref 1234 handle 102 matchall action drop
>     # tc filter show block 100
>     Cannot find block "100"
> 
> This patchset fixes this issue:
> 
>     # tc filter show block 100
>     filter protocol all pref 1234 matchall chain 0 
>     filter protocol all pref 1234 matchall chain 0 handle 0x66 
>       not_in_hw
>             action order 1: gact action drop
>              random type none pass val 0
>              index 2 ref 1 bind 1
> 
> In patch #1, the helpers and necessary infrastructure is introduced,
> including a new qdisc_util callback that implements sniffing out bound
> blocks in a given qdisc.
> 
> In patch #2, RED implements the new callback.
> 
> v3:
> - Patch #1:
>     - Do not pass &ctx->found directly to has_block. Do it through a
>       helper variable, so that the callee does not overwrite the result
>       already stored in ctx->found.
> 
> v2:
> - Patch #1:
>     - In tc_qdisc_block_exists_cb(), do not initialize 'q'.
>     - Propagate upwards errors from q->has_block.
> 
> Petr Machata (2):
>   tc: Look for blocks in qevents
>   tc: q_red: Implement has_block for RED
> 
>  tc/q_red.c     | 17 +++++++++++++++++
>  tc/tc_qdisc.c  | 18 ++++++++++++++++++
>  tc/tc_qevent.c | 15 +++++++++++++++
>  tc/tc_qevent.h |  2 ++
>  tc/tc_util.h   |  2 ++
>  5 files changed, 54 insertions(+)
> 


applied to iproute2-next. Thanks


      parent reply	other threads:[~2020-07-20 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 16:47 [PATCH iproute2-next v3 0/2] Support showing a block bound by qevent Petr Machata
2020-07-16 16:47 ` [PATCH iproute2-next v3 1/2] tc: Look for blocks in qevents Petr Machata
2020-07-17  6:16   ` Jiri Pirko
2020-07-16 16:47 ` [PATCH iproute2-next v3 2/2] tc: q_red: Implement has_block for RED Petr Machata
2020-07-20 16:37 ` David Ahern [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=1a00088f-7d25-082c-422c-b3c16bc15f67@gmail.com \
    --to=dsahern@gmail.com \
    --cc=jiri@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=petrm@mellanox.com \
    --cc=stephen@networkplumber.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.