From: Jakub Kicinski <kuba@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Jamal Hadi Salim <jhs@mojatatu.com>,
Ido Schimmel <idosch@idosch.org>,
netdev@vger.kernel.org, bpf@vger.kernel.org, victor@mojatatu.com,
martin.lau@linux.dev, dxu@dxuuu.xyz, xiyou.wangcong@gmail.com
Subject: Re: [PATCH net-next v2 1/2] net, sched: Make tc-related drop reason more flexible
Date: Wed, 25 Oct 2023 06:53:24 -0700 [thread overview]
Message-ID: <20231025065324.55fcd89e@kernel.org> (raw)
In-Reply-To: <87dfbac5-695c-7582-cbb5-4d71b6698ab1@iogearbox.net>
On Wed, 25 Oct 2023 13:52:43 +0200 Daniel Borkmann wrote:
> Ido, Jamal, wdyt about this alternative approach - these were the locations I could
> find from an initial glance (compile-tested) :
If we were to vote on which is better, I vote for this approach.
prev parent reply other threads:[~2023-10-25 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 9:26 [PATCH net-next v2 1/2] net, sched: Make tc-related drop reason more flexible Daniel Borkmann
2023-10-09 9:26 ` [PATCH net-next v2 2/2] net, sched: Add tcf_set_drop_reason for {__,}tcf_classify Daniel Borkmann
2023-10-09 14:03 ` [PATCH net-next v2 1/2] net, sched: Make tc-related drop reason more flexible Jamal Hadi Salim
2023-10-13 21:17 ` Jakub Kicinski
2023-10-16 20:10 ` patchwork-bot+netdevbpf
2023-10-25 8:59 ` Ido Schimmel
2023-10-25 10:01 ` Daniel Borkmann
2023-10-25 11:05 ` Jamal Hadi Salim
2023-10-25 11:52 ` Daniel Borkmann
2023-10-25 13:21 ` Jamal Hadi Salim
2023-10-25 13:46 ` Daniel Borkmann
2023-10-25 23:13 ` Jamal Hadi Salim
2023-10-27 14:01 ` Daniel Borkmann
2023-10-27 17:37 ` Jamal Hadi Salim
2023-10-27 18:29 ` Daniel Borkmann
2023-10-25 13:53 ` Jakub Kicinski [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=20231025065324.55fcd89e@kernel.org \
--to=kuba@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=idosch@idosch.org \
--cc=jhs@mojatatu.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=victor@mojatatu.com \
--cc=xiyou.wangcong@gmail.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.