[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpXLBrJggTQU3+MpdHPh1zQcN4T-HCTmqiPaKd6Cda-_2g@mail.gmail.com>
Date: Sun, 5 Jul 2020 17:28:55 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: Ariel Levkovich <lariel@...lanox.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...nulli.us>, Jiri Pirko <jiri@...lanox.com>,
Jakub Kicinski <kuba@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>
Subject: Re: [PATCH net-next v2 0/3] ] TC datapath hash api
On Sun, Jul 5, 2020 at 2:50 PM Jamal Hadi Salim <jhs@...atatu.com> wrote:
> BTW, nothing in skbedit is against computing what the new metadata
> should be.
Yup.
>
> IMO: A good arguement to not make it part of skbedit is if it adds
> unnecessary complexity to skbedit or policy definitions.
>
TCA_HASH_ALG_L4 literally has 4 lines of code, has no way
to add any unnecessary complexity to skbedit. (The BPF algorithm
does not belong to skbedit, obviously.)
Thanks.
Powered by blists - more mailing lists