All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francois Romieu <romieu@fr.zoreil.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.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: Wed, 6 Jul 2022 02:44:33 +0200	[thread overview]
Message-ID: <YsTa8QzSn/kMr5kk@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <20220705112713.644cf3b4@hermes.local>

Stephen Hemminger <stephen@networkplumber.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=AllRC
> > > 
> > > 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.

There are 1182 servers per
https://linux-hardware.org/?view=computers&type=Server

> 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??

Maxlinear keeps some archive material around:
https://www.maxlinear.com/Files/Documents/X3100Linux_GeneralInfo-FAQ.pdf

A search on linux-hardware with S2io vendor id from above (17d5) does
not find any part.

Patches aside, MARC does not find recent vxge material.

The driver is stable and the systems wherein it is used are (too) stable
as well. See for instance:

https://bugzilla.redhat.com/buglist.cgi?bug_status=__all__&content=vxge

Active maintenance seems useless.

-- 
Ueimor

  reply	other threads:[~2022-07-06  0:45 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
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 [this message]
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=YsTa8QzSn/kMr5kk@electric-eye.fr.zoreil.com \
    --to=romieu@fr.zoreil.com \
    --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=stephen@networkplumber.org \
    --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 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.