netdev - Re: [PATCH net-next V0 19/21] mlx4_core: Modify driver initialization flow to accommodate SRIOV for Ethernet

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <1323120413.2887.50.camel@bwh-desktop>
Date:	Mon, 5 Dec 2011 21:26:53 +0000
From:	Ben Hutchings <bhutchings@...arflare.com>
To:	Yevgeny Petrilin <yevgenyp@...lanox.co.il>
CC:	<davem@...emloft.net>, <netdev@...r.kernel.org>,
	<linux-rdma@...r.kernel.org>, <roland@...estorage.com>,
	<liranl@...lanox.co.il>, <jackm@....mellanox.co.il>
Subject: Re: [PATCH net-next V0 19/21] mlx4_core: Modify driver
 initialization flow to accommodate SRIOV for Ethernet

On Fri, 2011-12-02 at 12:19 +0200, Yevgeny Petrilin wrote:
> From: Jack Morgenstein <jackm@....mellanox.co.il>
> 
> 1. Added module parameters sr_iov and probe_vf for controlling enablement of
>    SRIOV mode.

This sort of option is useful in many drivers, and ideally would be
specified in some generic way rather than a module parameters.  However
I can't see a good way to make it configurable after the net device is
registered.

Currently the in-tree drivers have:

be2net: num_vfs
cxgb4:  num_vfs [array]
igb:    max_vfs
ixgbe:  max_vfs

Consider renaming 'sr_iov' to one of the above rather than adding to the
variation.

The 'probe_vf' parameter is very odd.  Why do you think it is necessary
to make this a module parameter?  It should be possible to bind and
unbind the driver from each VF dynamically via sysfs but this parameter
appears to restrict that.

[...]
> 3. Added port_type_array as a module parameter to allow driver startup with
>    ports configured as desired.
>    In SRIOV mode, only ETH is supported, and this array is ignored; otherwise,
>    for the case where the FW supports both port types (ETH and IB), the
>    port_type_array parameter is used.
>    By default, the port_type_array is set to configure both ports as IB.
[...]

You seem to be saying that this can be reconfigured after startup - in
which case is the module parameter really necessary?  Maybe I
misunderstand.

Ben.

-- 
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.

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