From: Ido Schimmel <idosch@idosch.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net, petrm@nvidia.com,
jiri@nvidia.com, amcohen@nvidia.com, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: Re: [PATCH net-next 0/5] mlxsw: Add support for RED qevent "mark"
Date: Sun, 24 Jan 2021 10:42:05 +0200 [thread overview]
Message-ID: <20210124084205.GA2819717@shredder.lan> (raw)
In-Reply-To: <20210123115527.58d0f04c@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
On Sat, Jan 23, 2021 at 11:55:27AM -0800, Jakub Kicinski wrote:
> On Sat, 23 Jan 2021 17:28:02 +0200 Ido Schimmel wrote:
> > > Thanks for the explanation. I feel more and more convinced now that
> > > we should have TC_ACT_TRAP_MIRROR and the devlink trap should only
> > > be on/off :S Current model of "if ACT_TRAP consult devlink for trap
> > > configuration" is impossible to model in SW since it doesn't have a
> > > equivalent of devlink traps. Or we need that equivalent..
> >
> > Wait, the current model is not "if ACT_TRAP consult devlink for trap
> > configuration". 'ecn_mark' action is always 'trap' ('mirror' in v2) and
> > can't be changed. Such packets can always be sent to the CPU, but the
> > decision of whether to send them or not is based on the presence of tc
> > filters attached to RED's 'mark' qevent with TC_ACT_TRAP
> > (TC_ACT_TRAP_MIRROR in v2).
>
> I see, missed that, but I think my point conceptually stands, right?
> Part of forwarding behavior was (in v1) only expressed in control
> plane (devlink) not dataplane (tc).
I don't think so? The action was set to 'trap' in both devlink and tc.
>
> > I believe that with the proposed changes in v2 it should be perfectly
> > clear that ECN marked packets are forwarded in hardware and a copy is
> > sent to the CPU.
>
> Yup, sounds good.
Thanks!
prev parent reply other threads:[~2021-01-24 8:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 8:02 [PATCH net-next 0/5] mlxsw: Add support for RED qevent "mark" Ido Schimmel
2021-01-17 8:02 ` [PATCH net-next 1/5] devlink: Add ecn_mark trap Ido Schimmel
2021-01-17 8:02 ` [PATCH net-next 2/5] mlxsw: spectrum_trap: " Ido Schimmel
2021-01-17 8:02 ` [PATCH net-next 3/5] mlxsw: spectrum_qdisc: Offload RED qevent mark Ido Schimmel
2021-01-17 8:02 ` [PATCH net-next 4/5] selftests: mlxsw: sch_red_core: Drop two unused variables Ido Schimmel
2021-01-17 8:02 ` [PATCH net-next 5/5] selftests: mlxsw: RED: Add selftests for the mark qevent Ido Schimmel
2021-01-19 22:22 ` [PATCH net-next 0/5] mlxsw: Add support for RED qevent "mark" Jakub Kicinski
2021-01-20 9:14 ` Ido Schimmel
2021-01-21 0:45 ` Jakub Kicinski
2021-01-21 10:23 ` Ido Schimmel
2021-01-21 17:19 ` Jakub Kicinski
2021-01-23 15:28 ` Ido Schimmel
2021-01-23 19:55 ` Jakub Kicinski
2021-01-24 8:42 ` Ido Schimmel [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=20210124084205.GA2819717@shredder.lan \
--to=idosch@idosch.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.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).