netdev - Re: [RFC v2] current devlink extension plan for NICs

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: <20200511053237.GB2245@nanopsycho>
Date:   Mon, 11 May 2020 07:32:37 +0200
From:   Jiri Pirko <jiri@...nulli.us>
To:     Dave Taht <dave.taht@...il.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>, parav@...lanox.com,
        yuvalav@...lanox.com, jgg@...pe.ca,
        Saeed Mahameed <saeedm@...lanox.com>, leon@...nel.org,
        andrew.gospodarek@...adcom.com, michael.chan@...adcom.com,
        moshe@...lanox.com, ayal@...lanox.com,
        Eran Ben Elisha <eranbe@...lanox.com>, vladbu@...lanox.com,
        kliteyn@...lanox.com, dchickles@...vell.com, sburla@...vell.com,
        fmanlunas@...vell.com, Tariq Toukan <tariqt@...lanox.com>,
        oss-drivers@...ronome.com, Shannon Nelson <snelson@...sando.io>,
        drivers@...sando.io, aelior@...vell.com,
        GR-everest-linux-l2@...vell.com, grygorii.strashko@...com,
        mlxsw <mlxsw@...lanox.com>, Ido Schimmel <idosch@...lanox.com>,
        markz@...lanox.com, jacob.e.keller@...el.com, valex@...lanox.com,
        linyunsheng@...wei.com, lihong.yang@...el.com,
        vikas.gupta@...adcom.com, sridhar.samudrala@...el.com
Subject: Re: [RFC v2] current devlink extension plan for NICs

Sun, May 10, 2020 at 06:30:59PM CEST, dave.taht@...il.com wrote:
>On Sun, May 10, 2020 at 7:46 AM Jiri Pirko <jiri@...nulli.us> wrote:
>>
>> Hello guys.
>>
>> Anyone has any opinion on the proposal? Or should I take it as a silent
>> agreement? :)
>>
>> We would like to go ahead and start sending patchsets.
>
>I gotta say that the whole thing makes my head really hurt, and while
>this conversation is about how to go about configuring things,
>I've been unable to get a grip on how flows will actually behave with
>these offloads present.

As you said, this is about configuration. Not the actual packet
processing.


>
>My overall starting point for thinking about this stuff was described
>in this preso to broadcom a few years back:
>http://flent-fremont.bufferbloat.net/~d/broadcom_aug9.pdf
>
>More recently I did what I think is my funniest talk ever on these
>subjects: https://blog.apnic.net/2020/01/22/bufferbloat-may-be-solved-but-its-not-over-yet/
>
>Make some popcorn, take a look. :) I should probably have covered
>ecn's (mis)behaviors at the end, but I didn't.
>
>Steven hemminger's lca talk on these subjects was also a riot...
>
>so somehow going from my understanding of how stuff gets configured,
>to the actual result, is needed, for me to have any opinion at all.
>You
>have this stuff basically running already? Can you run various
>flent.org tests through it?
>
>>
>> Thanks!
>
>
>
>-- 
>"For a successful technology, reality must take precedence over public
>relations, for Mother Nature cannot be fooled" - Richard Feynman
>
>dave@...t.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729