From: David Lamparter <equinox@diac24.net>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, corbet@lwn.net,
linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] eth: remove neterion/vxge
Date: Fri, 1 Jul 2022 16:11:38 +0200 [thread overview]
Message-ID: <Yr8Amo0lQzfia4+3@eidolon.nox.tf> (raw)
In-Reply-To: <Yr7/UwsV4mqg0I5t@nanopsycho>
On Fri, Jul 01, 2022 at 04:06:11PM +0200, Jiri Pirko wrote:
> Fri, Jul 01, 2022 at 03:17:32PM CEST, equinox@diac24.net wrote:
> >As a "reference datapoint", I'm a user that was affected by the removal
> >of the Mellanox SwitchX-2 driver about a year ago. But that was a bit
>
> You could not be. There was really no functionality implemented in
> switchx2 driver. I doubt you used 32x40G port switch with slow-path
> forwarding through kernel with total max bandwidth of like 1-2G for the
> whole switch :)
Funny you would mention that, that's exactly as far as I got - on some
attempts at least, when I didn't get an initialization failure after a
15 minute reset timer ;D
next prev parent reply other threads:[~2022-07-01 14:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 4:42 [PATCH net-next] eth: remove neterion/vxge Jakub Kicinski
2022-07-01 10:34 ` Jiri Pirko
2022-07-01 13:17 ` David Lamparter
2022-07-01 14:06 ` Jiri Pirko
2022-07-01 14:11 ` David Lamparter [this message]
2022-07-01 16:15 ` Jakub Kicinski
2022-07-04 8:24 ` Martin Habets
2022-07-01 17:12 ` Francois Romieu
2022-07-01 21:40 ` Jakub Kicinski
2022-07-05 6:17 ` Paolo Abeni
2022-07-05 18:06 ` Jakub Kicinski
2022-07-05 18:27 ` Stephen Hemminger
2022-07-06 0:44 ` Francois Romieu
2022-07-05 23:00 ` patchwork-bot+netdevbpf
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=Yr8Amo0lQzfia4+3@eidolon.nox.tf \
--to=equinox@diac24.net \
--cc=corbet@lwn.net \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.