[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c8028d330806131447t2b24be93sa0e07bfa792c8f7f@mail.gmail.com>
Date: Sat, 14 Jun 2008 03:17:08 +0530
From: "Amar Mudrankit" <amar.mudrankit@...gic.com>
To: "Patrick McHardy" <kaber@...sh.net>
Cc: netdev@...r.kernel.org, rdreier@...co.com,
general@...ts.openfabrics.org, poornima.kamath@...gic.com
Subject: Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation
>
> 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
--
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
Powered by blists - more mailing lists