From: Jakub Kicinski <kuba@kernel.org>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: Eric Garver <eric@garver.life>, Aaron Conole <aconole@redhat.com>,
netdev@vger.kernel.org, dev@openvswitch.org,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Adrian Moreno <amorenoz@redhat.com>,
Eelco Chaudron <echaudro@redhat.com>
Subject: Re: [ovs-dev] [PATCH net-next 2/2] net: openvswitch: add drop action
Date: Fri, 7 Jul 2023 08:00:25 -0700 [thread overview]
Message-ID: <20230707080025.7739e499@kernel.org> (raw)
In-Reply-To: <6060b37e-579a-76cb-b853-023cb1a25861@ovn.org>
On Fri, 7 Jul 2023 12:30:38 +0200 Ilya Maximets wrote:
> A wild idea: How about we do not define actual reasons? i.e. define a
> subsystem and just call kfree_skb_reason(skb, SUBSYSTEM | value), where
> 'value' is whatever userspace gives as long as it is within a subsystem
> range?
That already exists, right? Johannes added it in the last release for WiFi.
next prev parent reply other threads:[~2023-07-07 15:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 20:30 [PATCH net-next 0/2] net: openvswitch: add drop action Eric Garver
2023-06-29 20:30 ` [PATCH net-next 1/2] net: openvswitch: add drop reasons Eric Garver
2023-06-29 20:30 ` [PATCH net-next 2/2] net: openvswitch: add drop action Eric Garver
2023-06-29 22:46 ` kernel test robot
2023-06-29 22:56 ` kernel test robot
2023-06-30 9:47 ` Simon Horman
2023-06-30 12:29 ` Eric Garver
2023-06-30 13:25 ` [ovs-dev] " Simon Horman
2023-07-06 12:54 ` Aaron Conole
2023-07-06 13:57 ` Eric Garver
2023-07-07 10:30 ` Ilya Maximets
2023-07-07 15:00 ` Jakub Kicinski [this message]
2023-07-07 15:29 ` Ilya Maximets
2023-07-07 16:04 ` Ilya Maximets
2023-07-07 22:06 ` Jakub Kicinski
2023-07-10 16:51 ` Ilya Maximets
2023-07-10 17:01 ` Jakub Kicinski
2023-07-10 18:39 ` Ilya Maximets
2023-07-10 19:02 ` Jakub Kicinski
2023-07-10 18:21 ` Eric Garver
2023-07-11 20:46 ` Aaron Conole
2023-07-12 7:53 ` 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=20230707080025.7739e499@kernel.org \
--to=kuba@kernel.org \
--cc=aconole@redhat.com \
--cc=amorenoz@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=eric@garver.life \
--cc=i.maximets@ovn.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 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.