From: Aaron Conole <aconole@redhat.com>
To: Adrian Moreno <amorenoz@redhat.com>
Cc: netdev@vger.kernel.org, dev@openvswitch.org,
i.maximets@ovn.org, eric@garver.life,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 0/7] openvswitch: add drop reasons
Date: Mon, 24 Jul 2023 10:34:37 -0400 [thread overview]
Message-ID: <f7th6ptl6o2.fsf@redhat.com> (raw)
In-Reply-To: <20230722094238.2520044-1-amorenoz@redhat.com> (Adrian Moreno's message of "Sat, 22 Jul 2023 11:42:30 +0200")
Adrian Moreno <amorenoz@redhat.com> writes:
> There is currently a gap in drop visibility in the openvswitch module.
> This series tries to improve this by adding a new drop reason subsystem
> for OVS.
>
> Apart from adding a new drop reasson subsystem and some common drop
> reasons, this series takes Eric's preliminary work [1] on adding an
> explicit drop action and integrates it into the same subsystem.
>
> This series also adds some selftests and so it requires [2] to be
> applied first.
>
> A limitation of this series is that it does not report upcall errors.
> The reason is that there could be many sources of upcall drops and the
> most common one, which is the netlink buffer overflow, cannot be
> reported via kfree_skb() because the skb is freed in the netlink layer
> (see [3]). Therefore, using a reason for the rare events and not the
> common one would be even more misleading. I'd propose we add (in a
> follow up patch) a tracepoint to better report upcall errors.
I guess you meant to add RFC tag to this, since it depends on other
series that aren't accepted yet.
If it's okay, I will pull in your patch 5/7 when I re-post my flow
additions series, since it will need to be added there at some point
anyway.
> [1] https://lore.kernel.org/netdev/202306300609.tdRdZscy-lkp@intel.com/T/
> [2] https://lore.kernel.org/all/9375ccbc-dd40-9998-dde5-c94e4e28f4f1@redhat.com/T/
> [3] commit 1100248a5c5c ("openvswitch: Fix double reporting of drops in dropwatch")
>
> Adrian Moreno (6):
> net: openvswitch: add datapath flow drop reason
> net: openvswitch: add meter drop reason
> net: openvswitch: add misc error drop reasons
> selftests: openvswitch: support key masks
> selftests: openvswitch: add drop reason testcase
> selftests: openvswitch: add explicit drop testcase
>
> Eric Garver (1):
> net: openvswitch: add explicit drop action
>
> include/net/dropreason.h | 6 +
> include/uapi/linux/openvswitch.h | 2 +
> net/openvswitch/actions.c | 40 ++++--
> net/openvswitch/conntrack.c | 3 +-
> net/openvswitch/datapath.c | 16 +++
> net/openvswitch/drop.h | 33 +++++
> net/openvswitch/flow_netlink.c | 8 +-
> .../selftests/net/openvswitch/openvswitch.sh | 92 +++++++++++++-
> .../selftests/net/openvswitch/ovs-dpctl.py | 115 ++++++++++++------
> 9 files changed, 267 insertions(+), 48 deletions(-)
> create mode 100644 net/openvswitch/drop.h
next prev parent reply other threads:[~2023-07-24 14:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 9:42 [PATCH net-next 0/7] openvswitch: add drop reasons Adrian Moreno
2023-07-22 9:42 ` [PATCH net-next 1/7] net: openvswitch: add datapath flow drop reason Adrian Moreno
2023-07-22 9:42 ` [PATCH net-next 2/7] net: openvswitch: add explicit drop action Adrian Moreno
2023-07-24 14:47 ` Aaron Conole
2023-07-26 8:31 ` Adrian Moreno
2023-07-22 9:42 ` [PATCH net-next 3/7] net: openvswitch: add meter drop reason Adrian Moreno
2023-07-22 9:42 ` [PATCH net-next 4/7] net: openvswitch: add misc error drop reasons Adrian Moreno
2023-07-24 15:23 ` Aaron Conole
2023-07-26 8:32 ` Adrian Moreno
2023-07-22 9:42 ` [PATCH net-next 5/7] selftests: openvswitch: support key masks Adrian Moreno
2023-07-22 9:42 ` [PATCH net-next 6/7] selftests: openvswitch: add drop reason testcase Adrian Moreno
2023-07-22 9:42 ` [PATCH net-next 7/7] selftests: openvswitch: add explicit drop testcase Adrian Moreno
2023-07-24 14:49 ` Aaron Conole
2023-07-24 14:34 ` Aaron Conole [this message]
2023-07-26 8:34 ` [PATCH net-next 0/7] openvswitch: add drop reasons Adrian Moreno
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=f7th6ptl6o2.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=eric@garver.life \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).