lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Sat, 8 Oct 2022 08:32:22 -0400
From:   Jamal Hadi Salim <>
To:     Marcelo Leitner <>
Cc:     Davide Caratti <>,
        Ilya Maximets <>,
        Eelco Chaudron <>,
        Tianyu Yuan <>,
        Simon Horman <>,,
        oss-drivers <>,,
        Cong Wang <>,
        Oz Shlomo <>, Paul Blakey <>,
        Vlad Buslov <>
Subject: Re: [ovs-dev] [PATCH] tests: fix reference output for meter offload stats

On Fri, Oct 7, 2022 at 1:37 PM Marcelo Leitner <> wrote:
> On Fri, Oct 07, 2022 at 11:59:42AM -0400, Jamal Hadi Salim wrote:
> > On Fri, Oct 7, 2022 at 11:01 AM Marcelo Leitner <> wrote:
> > >

> >
> > It's mostly how people who offload (not sure about OVS) do it;
> > example some of the switches out there.
> You mean with OK, DROP, TRAP or GOTO actions, right?
> Because for PIPE, it has:
>                 } else if (is_tcf_gact_pipe(act)) {
>                         NL_SET_ERR_MSG_MOD(extack, "Offload of
> \"pipe\" action is not supported");
>                         return -EOPNOTSUPP;

I thought it was pipe but maybe it is OK(in my opinion that is a bad code
for just "count"). We have some (at least NIC) hardware folks on the list.
Note: we could create an alias to PIPE and call it COUNT if it helps.
And yes, in retrospect we should probably have separated out accounting
from the actions in tc. It makes a lot of sense in s/w - and would work fine for
modern hardware but when you dont have as many counters as actions
it's a challenge. Same thing with policers/meters.


Powered by blists - more mailing lists