netdev - Re: Fwd: [ofa-general] FW: QLogic vNIC Kernel Submission

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]

Date:	Tue, 17 Jun 2008 12:14:41 -0700
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Patrick McHardy <kaber@...sh.net>
Cc:	Amar Mudrankit <amar.mudrankit@...gic.com>, netdev@...r.kernel.org,
	rdreier@...co.com,
	Ramachandra K <ramachandra.kuchimanchi@...gic.com>,
	poornima.kamath@...gic.com
Subject: Re: Fwd: [ofa-general] FW: QLogic vNIC Kernel Submission

On Tue, 17 Jun 2008 20:34:59 +0200
Patrick McHardy <kaber@...sh.net> wrote:

> Amar Mudrankit wrote:
> > It looks as if my original email was "scrubbed" before it made the
> > mailing list so I am resending it...
> > 
> > QLogic has been attempting to submit our virtual NIC (vNIC) driver to
> > the Linux kernel for several months.  We have made changes to the code
> > based on the feedback we have received over four rounds of
> > submissions. Among the feedback we received during this process was a
> > request to alter our code to use a single value per file for
> > configuration of our driver through sysfs interface.  After spending
> > much time and effort to complete this change to our design we
> > re-submitted the driver only to receive a response suggesting that we
> > change once again from this interface to a different API interface
> > called rtnl_link.  Needless to say I am very frustrated with this
> > process. This new API interface would require substantial changes to
> > our code.
> 
> Thats one of the reasons why it should be done before merging it.
> The other one being that an API can't be removed easily once its
> in the kernel.

Understand that this is a community process and it isn't going to follow
a corporate model. There is no external pressures like schedules and users.
As Patrick said, there is also a sense of doing the right thing. The developers
would rather not repeat past mistakes, so are naturally hesitant on API's.
Adding a device that follows existing API's is always much easier. What you are
seeing is in part an internal discomfort with the plethora of API's and the binary
baggage of ioctl's, sysfs, etc.

If you could give a general outline of what the interface you want would do,
perhaps the community could provide some sample code that do what you want.
Netlink interfaces are less common, and there are fewer examples.
--
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