netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Amar Mudrankit" <amar.mudrankit@qlogic.com>
To: "Patrick McHardy" <kaber@trash.net>
Cc: netdev@vger.kernel.org, rdreier@cisco.com,
	general@lists.openfabrics.org, poornima.kamath@qlogic.com
Subject: Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation
Date: Sat, 14 Jun 2008 03:17:08 +0530	[thread overview]
Message-ID: <c8028d330806131447t2b24be93sa0e07bfa792c8f7f@mail.gmail.com> (raw)
In-Reply-To: <48529027.1090309@trash.net>

>
> If you have questions, feel free to ask.
>
I was trying to guess the use case for the vlan which has implemented
rtnl_link api :

For sending parameters to driver:
# ip link set <vlan-iface-name> up multicast ...... type vlan id
<vlan-id> reorder_hdr on

ingress-qos-map <...> egress-qos-map <...>

In such case, I think the link_util's private parse_opt function will
be invoked to parse link's private configurable parameters.  These
parameters along with the standard set of parameters (name, multicast,
promisc etc) are then sent to driver through rtnl_talk function .

Similarly, for reading values from driver:

# ip addr show dev <vlan-iface-name>

does it require "type" field similar to "ip link set"?

Is this understanding correct?

How does a link type corresponding to VLAN driver gets added into
linkutil_list, so that ip will correctly call functions specific to
VLAN driver?

>
> You can dump driver private statistics in the ->fill_xstats function.
>

I was looking at latest release of iproute2, in which I could not
locate fill_xstats. Can you help me to locate this?

Thanks and Regards,
Amar

  reply	other threads:[~2008-06-13 21:47 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 21:02 [ofa-general] [PATCH v4 00/14] QLogic VNIC Driver Ramachandra K
2008-06-10 21:02 ` [ofa-general] [PATCH v4 01/14] QLogic VNIC: Driver - netdev implementation Ramachandra K
2008-06-10 21:03 ` [ofa-general] [PATCH v4 02/14] QLogic VNIC: Netpath - abstraction of connection to EVIC/VEx Ramachandra K
2008-06-10 21:03 ` [ofa-general] [PATCH v4 03/14] QLogic VNIC: Implementation of communication protocol with EVIC/VEx Ramachandra K
2008-06-10 21:04 ` [ofa-general] [PATCH v4 04/14] QLogic VNIC: Implementation of Control path of communication protocol Ramachandra K
2008-06-10 22:21   ` Stephen Hemminger
2008-06-10 21:04 ` [ofa-general] [PATCH v4 05/14] QLogic VNIC: Implementation of Data " Ramachandra K
2008-06-10 21:05 ` [ofa-general] [PATCH v4 06/14] QLogic VNIC: IB core stack interaction Ramachandra K
2008-06-10 21:05 ` [ofa-general] [PATCH v4 07/14] QLogic VNIC: Handling configurable parameters of the driver Ramachandra K
2008-06-10 21:06 ` [ofa-general] [PATCH v4 08/14] QLogic VNIC: sysfs interface implementation for " Ramachandra K
2008-06-10 21:06 ` [ofa-general] [PATCH v4 09/14] QLogic VNIC: IB Multicast for Ethernet broadcast/multicast Ramachandra K
2008-06-10 21:07 ` [ofa-general] [PATCH v4 10/14] QLogic VNIC: Driver Statistics collection Ramachandra K
2008-06-10 21:07 ` [PATCH v4 11/14] QLogic VNIC: Driver utility file - implements various utility macros Ramachandra K
2008-06-10 21:08 ` [PATCH v4 12/14] QLogic VNIC: Driver Kconfig and Makefile Ramachandra K
2008-06-10 21:08 ` [ofa-general] [PATCH v4 13/14] QLogic VNIC: Modifications to IB " Ramachandra K
2008-06-10 21:09 ` [ofa-general] [PATCH v4 14/14] QLogic VNIC: sysfs Documentation Ramachandra K
2008-06-11  6:47   ` Patrick McHardy
2008-06-12 15:13     ` [ofa-general] " Amar Mudrankit
2008-06-12 15:18       ` Patrick McHardy
2008-06-12 15:29         ` Ramachandra K
2008-06-12 15:34           ` Patrick McHardy
2008-06-12 20:22           ` Jeff Garzik
2008-06-14 18:03         ` Roland Dreier
2008-06-14 19:03           ` Jason Gunthorpe
2008-06-16  8:54             ` Patrick McHardy
2008-06-18 12:32               ` Ramachandra K
2008-06-18 12:38                 ` Patrick McHardy
2008-06-18 18:21                   ` Jason Gunthorpe
2008-06-19  1:19                     ` Patrick McHardy
2008-06-19  1:26                       ` Patrick McHardy
2008-06-12 15:50     ` Ramachandra K
2008-06-12 16:03       ` Patrick McHardy
2008-06-12 21:09         ` Amar Mudrankit
2008-06-13 15:20           ` Patrick McHardy
2008-06-13 21:47             ` Amar Mudrankit [this message]
2008-06-14  8:08               ` Patrick McHardy
2008-06-16 19:44                 ` Amar Mudrankit
2008-06-16 20:39                   ` Patrick McHardy
2008-06-12 16:04       ` Karen Shaeffer
2008-06-12 15:21 ` [ofa-general] [PATCH v4 00/14] QLogic VNIC Driver Ramachandra K
2008-06-12 15:35   ` 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=c8028d330806131447t2b24be93sa0e07bfa792c8f7f@mail.gmail.com \
    --to=amar.mudrankit@qlogic.com \
    --cc=general@lists.openfabrics.org \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=poornima.kamath@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).