netdev - Re: [PATCH net-next V1 0/3] net/mlx4_core: Allow setting init-time device specific parameters

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]

Message-ID: <CAJ3xEMibyF7B3m2nrgBE8Zaj+oH+cJ+MH_61QfvO-ge=3CWYkQ@mail.gmail.com>
Date:	Thu, 12 Mar 2015 22:51:32 +0200
From:	Or Gerlitz <gerlitz.or@...il.com>
To:	David Miller <davem@...hat.com>
Cc:	hadarh@....mellanox.co.il,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Amir Vadai <amirv@...lanox.com>,
	Linux Netdev List <netdev@...r.kernel.org>,
	Hadar Hen Zion <hadarh@...lanox.com>,
	Yevgeny Petrilin <yevgenyp@...lanox.com>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	"talal@...lanox.com" <talal@...lanox.com>,
	Shannon Nelson <shannon.nelson@...el.com>,
	Doug Ledford <dledford@...hat.com>, greearb@...delatech.com,
	Greg Rose <gregory.v.rose@...el.com>,
	Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
	Jesse Brandeburg <jesse.brandeburg@...el.com>,
	john.ronciak@...el.com
Subject: Re: [PATCH net-next V1 0/3] net/mlx4_core: Allow setting init-time
 device specific parameters

On Thu, Mar 12, 2015 at 9:31 PM, David Miller <davem@...hat.com> wrote:
> From: Hadar Hen Zion <hadarh@....mellanox.co.il>
>> On Thu, Mar 12, 2015 at 8:05 PM, David Miller <davem@...emloft.net> wrote:
>>> From: Hadar Hen Zion <hadarh@....mellanox.co.il>
>>>> On Wed, Mar 11, 2015 at 7:14 PM, David Miller <davem@...emloft.net>

[...]
>>>>> These textual interfaces are arbitrary, and you are choosing it only
>>>>> because you cannot come up with a more reasonable scheme,

[...]
>>>> Is a scheme based on netlink will be acceptable by you?

>>> A portable, well typed, interface that other vendors could use if their
>>> hardware had similar features would be acceptable.

>> Do you mean an interface implementation that reminds the ethtool
>> private flags scheme but implemented through netlink, allows
>> configuration without a netdevice and more flexibility?

> I mean exactly what I said, neither more nor less.

Hey Dave, we're trying to see we understand... already two
implementations in a row weren't accepted, so now before doing the 3rd
one, we want to better align.

So, it has to be non-textual, portable, well typed and one that can be
used by other vendors too. We are talking that could be used for
multiple vendor driver to configure few proprietary HW initialization
params. So how about a scheme based on key/value pairs carried over
netlink messages?

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