netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ramachandra K" <ramachandra.kuchimanchi@qlogic.com>
To: "Stephen Hemminger" <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org, rdreier@cisco.com,
	amar.mudrankit@qlogic.com, general@lists.openfabrics.org,
	poornima.kamath@qlogic.com
Subject: Re: [ofa-general] Re: [PATCH v3 01/13] QLogic VNIC: Driver - netdev implementation
Date: Tue, 3 Jun 2008 17:44:23 +0530	[thread overview]
Message-ID: <71d336490806030514k580418e3n23790eb793e99381@mail.gmail.com> (raw)
In-Reply-To: <20080529102752.584147ee@extreme>

On Thu, May 29, 2008 at 10:57 PM, Stephen Hemminger
<shemminger@vyatta.com> wrote:
> On Thu, 29 May 2008 15:24:23 +0530
> Ramachandra K <ramachandra.kuchimanchi@qlogic.com> wrote:

<snip>
>
>> +module_param(vnic_debug, uint, 0444);
>> +MODULE_PARM_DESC(vnic_debug, "Enable debug tracing if > 0");
>
> maybe migrate this to ethtool msg_level?
>

We investigated this and found that we cannot map all of our Infiniband
level communication errors etc to the ethtool message levels. One option could
be to add support for Ethtool message levels in addition to the vnic_debug
controlled messages. The Ethtool support would make this driver conform
to ethtool similar to other Ethernet drivers and the vnic_debug messages will
help in debugging the Infiniband related errors.

Is ethtool support mandatory for a merge to 2.6.27 or can we consider
it as a future
enhancement while we first focus on moving this driver to use CONFIGFS ?

Regards,
Ram

  reply	other threads:[~2008-06-03 12:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-29  9:53 [PATCH v3 00/13] QLogic VNIC Driver Ramachandra K
2008-05-29  9:54 ` [ofa-general] [PATCH v3 01/13] QLogic VNIC: Driver - netdev implementation Ramachandra K
2008-05-29 17:27   ` [ofa-general] " Stephen Hemminger
2008-06-03 12:14     ` Ramachandra K [this message]
2008-06-03 17:51       ` Stephen Hemminger
2008-05-29  9:54 ` [ofa-general] [PATCH v3 02/13] QLogic VNIC: Netpath - abstraction of connection to EVIC/VEx Ramachandra K
2008-05-29  9:55 ` [ofa-general] [PATCH v3 03/13] QLogic VNIC: Implementation of communication protocol with EVIC/VEx Ramachandra K
2008-05-29  9:55 ` [ofa-general] [PATCH v3 04/13] QLogic VNIC: Implementation of Control path of communication protocol Ramachandra K
2008-05-29  9:56 ` [ofa-general] [PATCH v3 05/13] QLogic VNIC: Implementation of Data " Ramachandra K
2008-05-29  9:56 ` [ofa-general] [PATCH v3 06/13] QLogic VNIC: IB core stack interaction Ramachandra K
2008-05-29  9:57 ` [ofa-general] [PATCH v3 07/13] QLogic VNIC: Handling configurable parameters of the driver Ramachandra K
2008-05-29  9:57 ` [ofa-general] [PATCH v3 08/13] QLogic VNIC: sysfs interface implementation for " Ramachandra K
2008-05-29 17:30   ` [ofa-general] " Stephen Hemminger
2008-05-29 17:48     ` Greg KH
2008-06-01  5:46       ` Roland Dreier
2008-06-03 12:24         ` [ofa-general] " Ramachandra K
2008-06-03 15:10           ` Roland Dreier
2008-06-03 18:25       ` Amar Mudrankit
2008-06-03 18:30         ` Greg KH
2008-06-03 18:45         ` David Dillow
2008-06-05  4:10           ` Roland Dreier
2008-06-05  5:40             ` Dave Dillow
2008-06-05 16:38               ` Roland Dreier
2008-06-05 17:01                 ` Stephen Hemminger
2008-06-05 17:32                   ` Patrick McHardy
2008-06-05 20:47                     ` Roland Dreier
2008-06-05 22:54                       ` Patrick McHardy
2008-06-05 17:54                 ` David Dillow
2008-05-29  9:58 ` [ofa-general] [PATCH v3 09/13] QLogic VNIC: IB Multicast for Ethernet broadcast/multicast Ramachandra K
2008-05-29  9:58 ` [ofa-general] [PATCH v3 10/13] QLogic VNIC: Driver Statistics collection Ramachandra K
2008-05-29  9:59 ` [PATCH v3 11/13] QLogic VNIC: Driver utility file - implements various utility macros Ramachandra K
2008-05-29  9:59 ` [ofa-general] [PATCH v3 12/13] QLogic VNIC: Driver Kconfig and Makefile Ramachandra K
2008-05-29 10:00 ` [ofa-general] [PATCH v3 13/13] QLogic VNIC: Modifications to IB " Ramachandra K

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=71d336490806030514k580418e3n23790eb793e99381@mail.gmail.com \
    --to=ramachandra.kuchimanchi@qlogic.com \
    --cc=amar.mudrankit@qlogic.com \
    --cc=general@lists.openfabrics.org \
    --cc=netdev@vger.kernel.org \
    --cc=poornima.kamath@qlogic.com \
    --cc=rdreier@cisco.com \
    --cc=shemminger@vyatta.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).