netdev - Re: [ofa-general] Re: [PATCH v4 14/14] QLogic VNIC: sysfs Documentation

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]

Message-ID: <48537C68.1010207@trash.net>
Date:	Sat, 14 Jun 2008 10:08:08 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Amar Mudrankit <amar.mudrankit@...gic.com>
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

Amar Mudrankit wrote:
>> 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"?

No. Thats only required for parsing device specific parameters.

> Is this understanding correct?

Yes.

> 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?

iproute dlopens itself and looks for the struct "<type>_link_util".

>> 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?

->fill_xstats is in the kernel, in iproute its ->print_xstats.
--
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