From: Jiri Pirko <jiri@resnulli.us>
To: Dave Taht <dave.taht@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
parav@mellanox.com, yuvalav@mellanox.com, jgg@ziepe.ca,
Saeed Mahameed <saeedm@mellanox.com>,
leon@kernel.org, andrew.gospodarek@broadcom.com,
michael.chan@broadcom.com, moshe@mellanox.com, ayal@mellanox.com,
Eran Ben Elisha <eranbe@mellanox.com>,
vladbu@mellanox.com, kliteyn@mellanox.com, dchickles@marvell.com,
sburla@marvell.com, fmanlunas@marvell.com,
Tariq Toukan <tariqt@mellanox.com>,
oss-drivers@netronome.com, Shannon Nelson <snelson@pensando.io>,
drivers@pensando.io, aelior@marvell.com,
GR-everest-linux-l2@marvell.com, grygorii.strashko@ti.com,
mlxsw <mlxsw@mellanox.com>, Ido Schimmel <idosch@mellanox.com>,
markz@mellanox.com, jacob.e.keller@intel.com, valex@mellanox.com,
linyunsheng@huawei.com, lihong.yang@intel.com,
vikas.gupta@broadcom.com, sridhar.samudrala@intel.com
Subject: Re: [RFC v2] current devlink extension plan for NICs
Date: Mon, 11 May 2020 07:32:37 +0200 [thread overview]
Message-ID: <20200511053237.GB2245@nanopsycho> (raw)
In-Reply-To: <CAA93jw7ROwOhZNS+dREeFurjn=YxUVWStL+WKZxHgZFLRX+X0w@mail.gmail.com>
Sun, May 10, 2020 at 06:30:59PM CEST, dave.taht@gmail.com wrote:
>On Sun, May 10, 2020 at 7:46 AM Jiri Pirko <jiri@resnulli.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@taht.net <Dave Täht> CTO, TekLibre, LLC Tel: 1-831-435-0729
next prev parent reply other threads:[~2020-05-11 5:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 9:14 [RFC v2] current devlink extension plan for NICs Jiri Pirko
2020-05-04 2:12 ` Samudrala, Sridhar
2020-05-04 11:42 ` Jiri Pirko
2020-05-10 14:45 ` Jiri Pirko
2020-05-10 16:30 ` Dave Taht
2020-05-11 5:32 ` Jiri Pirko [this message]
2020-05-11 22:37 ` Jacob Keller
2020-05-13 13:00 ` [oss-drivers] " Simon Horman
2020-05-14 6:07 ` Jiri Pirko
2020-05-14 23:52 ` Jacob Keller
2020-05-15 9:30 ` Jiri Pirko
2020-05-15 21:36 ` Jacob Keller
2020-05-18 6:52 ` Jiri Pirko
2020-05-18 21:05 ` Jacob Keller
2020-05-19 5:17 ` Parav Pandit
2020-05-19 19:45 ` Jacob Keller
2020-05-20 12:58 ` Parav Pandit
2020-05-19 5:19 ` Jiri Pirko
2020-05-19 9:22 ` [RFC v3] " Jiri Pirko
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=20200511053237.GB2245@nanopsycho \
--to=jiri@resnulli.us \
--cc=GR-everest-linux-l2@marvell.com \
--cc=aelior@marvell.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=ayal@mellanox.com \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=dchickles@marvell.com \
--cc=drivers@pensando.io \
--cc=eranbe@mellanox.com \
--cc=fmanlunas@marvell.com \
--cc=grygorii.strashko@ti.com \
--cc=idosch@mellanox.com \
--cc=jacob.e.keller@intel.com \
--cc=jgg@ziepe.ca \
--cc=kliteyn@mellanox.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=lihong.yang@intel.com \
--cc=linyunsheng@huawei.com \
--cc=markz@mellanox.com \
--cc=michael.chan@broadcom.com \
--cc=mlxsw@mellanox.com \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=parav@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=sburla@marvell.com \
--cc=snelson@pensando.io \
--cc=sridhar.samudrala@intel.com \
--cc=tariqt@mellanox.com \
--cc=valex@mellanox.com \
--cc=vikas.gupta@broadcom.com \
--cc=vladbu@mellanox.com \
--cc=yuvalav@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).