From: Petr Machata <petrm@nvidia•com>
To: Daniel Machon <daniel.machon@microchip•com>
Cc: <netdev@vger•kernel.org>, <davem@davemloft•net>,
<edumazet@google•com>, <kuba@kernel•org>, <pabeni@redhat•com>,
<lars.povlsen@microchip•com>, <Steen.Hegelund@microchip•com>,
<UNGLinuxDriver@microchip•com>, <joe@perches•com>,
<error27@gmail•com>, <horatiu.vultur@microchip•com>,
<Julia.Lawall@inria•fr>, <petrm@nvidia•com>,
<vladimir.oltean@nxp•com>, <maxime.chevallier@bootlin•com>,
<linux-arm-kernel@lists•infradead.org>,
<linux-kernel@vger•kernel.org>
Subject: Re: [PATCH net-next v3 3/6] net: dcb: add new rewrite table
Date: Thu, 19 Jan 2023 09:59:37 +0100 [thread overview]
Message-ID: <87a62e98vp.fsf@nvidia.com> (raw)
In-Reply-To: <20230118210830.2287069-4-daniel.machon@microchip.com>
Daniel Machon <daniel.machon@microchip•com> writes:
> Add new rewrite table and all the required functions, offload hooks and
> bookkeeping for maintaining it. The rewrite table reuses the app struct,
> and the entire set of app selectors. As such, some bookeeping code can
> be shared between the rewrite- and the APP table.
>
> New functions for getting, setting and deleting entries has been added.
> Apart from operating on the rewrite list, these functions do not emit a
> DCB_APP_EVENT when the list os modified. The new dcb_getrewr does a
> lookup based on selector and priority and returns the protocol, so that
> mappings from priority to protocol, for a given selector and ifindex is
> obtained.
>
> Also, a new nested attribute has been added, that encapsulates one or
> more app structs. This attribute is used to distinguish the two tables.
>
> The dcb_lock used for the APP table is reused for the rewrite table.
>
> Signed-off-by: Daniel Machon <daniel.machon@microchip•com>
Reviewed-by: Petr Machata <petrm@nvidia•com>
next prev parent reply other threads:[~2023-01-19 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 21:08 [PATCH net-next v3 0/6] Introduce new DCB rewrite table Daniel Machon
2023-01-18 21:08 ` [PATCH net-next v3 1/6] net: dcb: modify dcb_app_add to take list_head ptr as parameter Daniel Machon
2023-01-19 9:22 ` Petr Machata
2023-01-18 21:08 ` [PATCH net-next v3 2/6] net: dcb: add new common function for set/del of app/rewr entries Daniel Machon
2023-01-19 9:21 ` Petr Machata
2023-01-18 21:08 ` [PATCH net-next v3 3/6] net: dcb: add new rewrite table Daniel Machon
2023-01-19 8:59 ` Petr Machata [this message]
2023-01-18 21:08 ` [PATCH net-next v3 4/6] net: dcb: add helper functions to retrieve PCP and DSCP rewrite maps Daniel Machon
2023-01-19 9:23 ` Petr Machata
2023-01-18 21:08 ` [PATCH net-next v3 5/6] net: microchip: sparx5: add support for PCP rewrite Daniel Machon
2023-01-18 21:08 ` [PATCH net-next v3 6/6] net: microchip: sparx5: add support for DSCP rewrite Daniel Machon
2023-01-20 12:30 ` [PATCH net-next v3 0/6] Introduce new DCB rewrite table patchwork-bot+netdevbpf
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=87a62e98vp.fsf@nvidia.com \
--to=petrm@nvidia$(echo .)com \
--cc=Julia.Lawall@inria$(echo .)fr \
--cc=Steen.Hegelund@microchip$(echo .)com \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=daniel.machon@microchip$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=error27@gmail$(echo .)com \
--cc=horatiu.vultur@microchip$(echo .)com \
--cc=joe@perches$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=lars.povlsen@microchip$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=maxime.chevallier@bootlin$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=vladimir.oltean@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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