From: Vlad Buslov <vladbu@nvidia•com>
To: Jamal Hadi Salim <jhs@mojatatu•com>
Cc: Simon Horman <simon.horman@corigine•com>,
David Miller <davem@davemloft•net>,
Jakub Kicinski <kuba@kernel•org>,
Cong Wang <xiyou.wangcong@gmail•com>,
Jiri Pirko <jiri@mellanox•com>, <netdev@vger•kernel.org>,
<oss-drivers@corigine•com>,
Baowen Zheng <baowen.zheng@corigine•com>,
Louis Peens <louis.peens@corigine•com>,
"Ido Schimmel" <idosch@nvidia•com>, Jiri Pirko <jiri@resnulli•us>,
Roopa Prabhu <roopa@nvidia•com>
Subject: Re: tc offload debug-ability
Date: Tue, 3 Aug 2021 15:14:58 +0300 [thread overview]
Message-ID: <ygnhsfzqpvwd.fsf@nvidia.com> (raw)
In-Reply-To: <996ecc2d-d982-c7f3-7769-3b489d5ff66c@mojatatu.com>
On Tue 03 Aug 2021 at 15:02, Jamal Hadi Salim <jhs@mojatatu•com> wrote:
> I just changed the subject line..
>
> On 2021-08-03 5:57 a.m., Jamal Hadi Salim wrote:
>> On 2021-07-30 7:40 a.m., Vlad Buslov wrote:
>>> On Fri 30 Jul 2021 at 13:17, Jamal Hadi Salim <jhs@mojatatu•com> wrote:
>>>> On 2021-07-28 10:46 a.m., Simon Horman wrote:
>>
>>>
>>> Filters with tunnel_key encap actions can be offloaded/unoffloaded
>>> dynamically based on neigh state (see mlx5e_rep_neigh_update()) and fib
>>> events (see mlx5e_tc_fib_event_work()).
>>>
>> Thanks. Will look and compare against the FIB case.
>>
>
> So unless i am mistaken Vlad:
> a) there is no way to reflect the details when someone dumps the rules.
> b) No notifications sent to the control plane (user space) when the
> neighbor updates are offloaded.
Correct.
>
> My comments earlier are inspired by debugging tc offload and by this:
>
> https://patches.linaro.org/cover/378345/
>
> cheers,
> jamal
next prev parent reply other threads:[~2021-08-03 12:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 9:19 [PATCH net-next 0/3] flow_offload: hardware offload of TC actions Simon Horman
2021-07-22 9:19 ` [PATCH net-next 1/3] flow_offload: allow user to offload tc action to net device Simon Horman
2021-07-22 12:24 ` Roi Dayan
2021-07-22 13:19 ` Simon Horman
2021-07-22 13:29 ` Vlad Buslov
2021-07-22 13:33 ` Jamal Hadi Salim
2021-07-27 13:04 ` Simon Horman
2021-07-27 14:38 ` Vlad Buslov
2021-07-27 16:13 ` Jamal Hadi Salim
2021-07-27 16:47 ` Vlad Buslov
2021-07-28 7:46 ` Simon Horman
2021-07-28 8:05 ` Vlad Buslov
2021-07-28 13:51 ` Jamal Hadi Salim
2021-07-28 14:46 ` Simon Horman
2021-07-30 10:17 ` Jamal Hadi Salim
2021-07-30 11:40 ` Vlad Buslov
2021-08-03 9:57 ` Jamal Hadi Salim
2021-08-03 12:02 ` tc offload debug-ability Jamal Hadi Salim
2021-08-03 12:14 ` Vlad Buslov [this message]
2021-08-03 12:50 ` Jamal Hadi Salim
2021-08-03 13:34 ` Ido Schimmel
2021-07-30 13:20 ` [PATCH net-next 1/3] flow_offload: allow user to offload tc action to net device Simon Horman
2021-08-03 10:14 ` Jamal Hadi Salim
2021-08-03 11:36 ` Simon Horman
2021-08-03 11:45 ` Jamal Hadi Salim
2021-08-03 12:31 ` Simon Horman
2021-08-03 13:01 ` Jamal Hadi Salim
2021-08-03 14:46 ` Simon Horman
2021-07-22 13:57 ` kernel test robot
2021-07-22 15:31 ` kernel test robot
2021-08-03 10:50 ` Jamal Hadi Salim
2021-08-03 11:05 ` Jamal Hadi Salim
2021-08-03 11:31 ` Simon Horman
2021-07-22 9:19 ` [PATCH net-next 2/3] flow_offload: add process to delete offloaded actions from " Simon Horman
2021-07-22 14:25 ` Vlad Buslov
2021-07-22 14:50 ` kernel test robot
2021-07-22 17:07 ` kernel test robot
2021-08-03 10:59 ` Jamal Hadi Salim
2021-07-22 9:19 ` [PATCH net-next 3/3] flow_offload: add process to update action stats from hardware Simon Horman
2021-07-22 14:55 ` Vlad Buslov
2021-08-03 11:24 ` Jamal Hadi Salim
2021-08-03 11:35 ` Simon Horman
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=ygnhsfzqpvwd.fsf@nvidia.com \
--to=vladbu@nvidia$(echo .)com \
--cc=baowen.zheng@corigine$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=idosch@nvidia$(echo .)com \
--cc=jhs@mojatatu$(echo .)com \
--cc=jiri@mellanox$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=kuba@kernel$(echo .)org \
--cc=louis.peens@corigine$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=oss-drivers@corigine$(echo .)com \
--cc=roopa@nvidia$(echo .)com \
--cc=simon.horman@corigine$(echo .)com \
--cc=xiyou.wangcong@gmail$(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