From: Stephen Hemminger <stephen@networkplumber.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>,
Francois Romieu <romieu@fr.zoreil.com>,
davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
corbet@lwn.net, jdmason@kudzu.us, vburru@marvell.com,
jiawenwu@trustnetic.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next] eth: remove neterion/vxge
Date: Tue, 5 Jul 2022 11:27:13 -0700 [thread overview]
Message-ID: <20220705112713.644cf3b4@hermes.local> (raw)
In-Reply-To: <20220705110634.4a66389a@kernel.org>
On Tue, 5 Jul 2022 11:06:34 -0700
Jakub Kicinski <kuba@kernel.org> wrote:
> On Tue, 05 Jul 2022 08:17:24 +0200 Paolo Abeni wrote:
> > On Fri, 2022-07-01 at 14:40 -0700, Jakub Kicinski wrote:
> > > 100%, I really wish something like that existed. I have a vague memory
> > > of Fedora or some other distro collecting HW data. Maybe it died because
> > > of privacy issues?
> >
> > AFAICS that database still exists and is active:
> >
> > https://linux-hardware.org/?view=search&vendor=neterion&d=All
> >
> > It shows no usage at all for the relevant vendor.
> >
> > On the flip side, it looks like the data points come mostly/exclusively
> > from desktop systems, not very relevant in this specific case.
>
> GTK! There is a whole bunch of old Mellanox NICs reported so I think
> there is _some_ server coverage. I'm leaning towards applying the patch.
Looks like S2IO became Neterion and then was acquired by Exar in 2010.
Then MaxLinear acquired Exar in 2017.
Looks like they dropped out of NIC business and only do switches??
next prev parent reply other threads:[~2022-07-05 18:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220701044234.706229-1-kuba@kernel.org>
2022-07-01 10:34 ` [PATCH net-next] eth: remove neterion/vxge Jiri Pirko
2022-07-01 13:17 ` David Lamparter
2022-07-01 14:06 ` Jiri Pirko
2022-07-01 14:11 ` David Lamparter
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 [this message]
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=20220705112713.644cf3b4@hermes.local \
--to=stephen@networkplumber.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jdmason@kudzu.us \
--cc=jiawenwu@trustnetic.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=romieu@fr.zoreil.com \
--cc=vburru@marvell.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).