netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Amar Mudrankit <amar.mudrankit@qlogic.com>
Cc: netdev@vger.kernel.org, rdreier@cisco.com,
	Ramachandra K <ramachandra.kuchimanchi@qlogic.com>,
	poornima.kamath@qlogic.com
Subject: Re: Fwd: [ofa-general] FW: QLogic vNIC Kernel Submission
Date: Wed, 18 Jun 2008 06:43:46 -0400	[thread overview]
Message-ID: <4858E6E2.8050609@garzik.org> (raw)
In-Reply-To: <c8028d330806171018j7f129ddft3bee056e4be9b954@mail.gmail.com>

Amar Mudrankit wrote:
> ---------- Forwarded message ----------
> From: John Russo <john.russo@qlogic.com>
> Date: Tue, Jun 17, 2008 at 6:36 PM
> Subject: [ofa-general] FW: QLogic vNIC Kernel Submission
> To: general@lists.openfabrics.org
> 
> 
> 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.
> 
> QLogic has met the initial request to move to a single valued sysfs
> interface and I would hope that this new request will be waived and
> will not be a roadblock to inclusion of our driver to the kernel.

One option is to get the base driver into the tree, sans sysfs 
interface, and wait for the netlink interface.

As Patrick noted, it is very important to -not- just throw new user 
interfaces into the tree, because that essentially sets them in stone at 
that point, needing to be supported as an Application Binary Interface 
(ABI).

The other stuff, like duplication of existing interfaces and strange 
FSM-based netdev registration, are problems that could be worked out 
in-tree, I suppose.

	Jeff




  parent reply	other threads:[~2008-06-18 10:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <99863D2ED484D449811D97A4C44C9CBD7C50F7@EPEXCH2.qlogic.org>
2008-06-17 17:18 ` Fwd: [ofa-general] FW: QLogic vNIC Kernel Submission Amar Mudrankit
2008-06-17 18:34   ` Patrick McHardy
2008-06-17 19:14     ` Stephen Hemminger
     [not found]       ` <C07C40DB2364324799506DE8FF12F8D859E90D@EPEXCH1.qlogic.org>
2008-06-17 20:12         ` John Russo
2008-06-17 20:49           ` Patrick McHardy
2008-06-17 23:59             ` Jeff Garzik
2008-06-17 19:15     ` Patrick McHardy
2008-06-18 10:43   ` Jeff Garzik [this message]
2008-06-18 11:19     ` Patrick McHardy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4858E6E2.8050609@garzik.org \
    --to=jeff@garzik.org \
    --cc=amar.mudrankit@qlogic.com \
    --cc=netdev@vger.kernel.org \
    --cc=poornima.kamath@qlogic.com \
    --cc=ramachandra.kuchimanchi@qlogic.com \
    --cc=rdreier@cisco.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).