[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250318172026.GA9311@nvidia.com>
Date: Tue, 18 Mar 2025 14:20:26 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: "Samudrala, Sridhar" <sridhar.samudrala@...el.com>
Cc: Leon Romanovsky <leon@...nel.org>,
"Ertman, David M" <david.m.ertman@...el.com>,
Jakub Kicinski <kuba@...nel.org>,
"Nikolova, Tatyana E" <tatyana.e.nikolova@...el.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [Intel-wired-lan] [iwl-next v4 1/1] iidc/ice/irdma: Update IDC
to support multiple consumers
On Tue, Mar 18, 2025 at 10:01:36AM -0700, Samudrala, Sridhar wrote:
> Yes. Today irdma uses exported symbols from i40e and ice and loading irdma
> results in both modules to be loaded even when only type of NIC is present
> on a system. This series is trying to remove that dependency by using
> callbacks.
If you really have two different core drivers that can provide the
same API then I think you are stuck with function pointers :\
It is really weird though, why are their two core drivers that can
provide the same API? Is this because intel keeps rewriting their
driver stack every few years?
Jason
Powered by blists - more mailing lists