lists.openwall.net   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  linux-cve-announce  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]
Message-ID: <CAM0EoMnKk9=WFm7ZtPbHDRc6_J7Xw8WR3TG2_Em4ucJ6nCNJOw@mail.gmail.com>
Date:   Tue, 31 Jan 2023 17:32:52 -0500
From:   Jamal Hadi Salim <jhs@...atatu.com>
To:     Jakub Kicinski <kuba@...nel.org>
Cc:     John Fastabend <john.fastabend@...il.com>,
        "Singhai, Anjali" <anjali.singhai@...el.com>,
        Toke Høiland-Jørgensen <toke@...hat.com>,
        Jamal Hadi Salim <hadi@...atatu.com>,
        Jiri Pirko <jiri@...nulli.us>,
        Willem de Bruijn <willemb@...gle.com>,
        Stanislav Fomichev <sdf@...gle.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "kernel@...atatu.com" <kernel@...atatu.com>,
        "Chatterjee, Deb" <deb.chatterjee@...el.com>,
        "Limaye, Namrata" <namrata.limaye@...el.com>,
        "khalidm@...dia.com" <khalidm@...dia.com>,
        "tom@...anda.io" <tom@...anda.io>,
        "pratyush@...anda.io" <pratyush@...anda.io>,
        "xiyou.wangcong@...il.com" <xiyou.wangcong@...il.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "edumazet@...gle.com" <edumazet@...gle.com>,
        "pabeni@...hat.com" <pabeni@...hat.com>,
        "vladbu@...dia.com" <vladbu@...dia.com>,
        "simon.horman@...igine.com" <simon.horman@...igine.com>,
        "stefanc@...vell.com" <stefanc@...vell.com>,
        "seong.kim@....com" <seong.kim@....com>,
        "mattyk@...dia.com" <mattyk@...dia.com>,
        "Daly, Dan" <dan.daly@...el.com>,
        "Fingerhut, John Andy" <john.andy.fingerhut@...el.com>
Subject: Re: [PATCH net-next RFC 00/20] Introducing P4TC

On Tue, Jan 31, 2023 at 2:10 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Tue, 31 Jan 2023 05:30:10 -0500 Jamal Hadi Salim wrote:
> > > Note, there are two paths in P4TC:
> > > DDP loading via devlink is equivalent to loading the P4 binary for the hardware.
> > > That is one of the 3 (and currently most popular) driver interfaces
> > > suggested. Some of that drew
> >
> > Sorry didnt finish my thought here, wanted to say: The loading of the
> > P4 binary over devlink drew (to some people) suspicion it is going to
> > be used for loading kernel bypass.
>
> The only practical use case I heard was the IPU. Worrying about devlink
> programming being a bypass on an IPU is like rearranging chairs on the
> Titanic.

BTW, I do believe FNICs are heading in that direction as well. I didnt
quiet follow the titanic chairs analogy, can you elaborate on that
statement?

cheers,
jamal

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ