netdev - Re: [PATCH] mlx4_en: added pci_device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 11 Jun 2009 16:17:54 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	yevgenyp@...lanox.co.il
Cc:	rdreier@...co.com, netdev@...r.kernel.org, tziporet@...lanox.co.il
Subject: Re: [PATCH] mlx4_en: added pci_device_id table

From: Yevgeny Petrilin <yevgenyp@...lanox.co.il>
Date: Thu, 11 Jun 2009 17:40:05 +0300

> As for combining the modules, it is not something we would like to
> do.  mlx4_en module is not the only "customer" of mlx4_core, there
> is also mlx4_ib and mlx4_fc (in the near future).  According to our
> design, the mlx4_core module is protocol independent and gives
> services (like command interface and HW resources management) to the
> modules mentioned above.

Other drivers handle this IB usage of a networking device core more
elegantly, I'm pretty sure.

There is nothing that prevents you from making the mlx4_en networking
device driver be one module and export symbols that the IB driver can
make use of.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html