gnet_stats_start_copy_compat(9) [suse man page]

GNET_STATS_START_COP(9) 					 Linux Networking					   GNET_STATS_START_COP(9)

NAME

       gnet_stats_start_copy_compat - start dumping procedure in compatibility mode

SYNOPSIS

       int gnet_stats_start_copy_compat(struct sk_buff * skb, int type, int tc_stats_type, int xstats_type, spinlock_t * lock,
					struct gnet_dump * d);

ARGUMENTS

       skb
	   socket buffer to put statistics TLVs into

       type
	   TLV type for top level statistic TLV

       tc_stats_type
	   TLV type for backward compatibility struct tc_stats TLV

       xstats_type
	   TLV type for backward compatibility xstats TLV

       lock
	   statistics lock

       d
	   dumping handle

DESCRIPTION

       Initializes the dumping handle, grabs the statistic lock and appends an empty TLV header to the socket buffer for use a container for all
       other statistic TLVS.

       The dumping handle is marked to be in backward compatibility mode telling all gnet_stats_copy_XXX functions to fill a local copy of struct
       tc_stats.

       Returns 0 on success or -1 if the room in the socket buffer was not sufficient.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						   GNET_STATS_START_COP(9)

lldptool(8)							       Linux							       lldptool(8)

NAME

       APP - Show / manipulate APP TLV configuration

SYNOPSIS

       lldptool -t -i ethx -V APP [-c app]

       lldptool -T -i ethx -V APP [-d] app=prio,sel,pid

DESCRIPTION

       The  APP  TLV  is an informational TLV and will advertise the current configured application table. If the peer APP TLV and a local APP TLV
       match the same selector and protocol field the local parameter is used.

ARGUMENTS

       app    Configures a local application data field using the three parameters: priority (prio), selector (sel), and protocol  (pid).  The	-d
	      option can be provided to remove an entry which matches the three parameters.

Theory of Operations
       The  APP  TLV is an informational TLV for most end stations. It is not expected that setting APP data should be required. Peer data will be
       processed and added to the application data table by default assuming there does not already exist a local entry with matching selector and
       priority fields.

       By adding APP data to the application table it is available for applications, eg iscsid, to query. Applications query for a specific proto-
       col and selector and may use this data to map traffic to the corresponding traffic class.

EXAMPLE &; USAGE
       Configure ISCSI application for priority 4 on eth2
	      lldptool -T -i eth2 -V APP app=4,2,3260

       Configure FCoE application for priority 3 on eth2
	      lldptool -T -i eth2 -V APP app=3,1,35078

       Remove FCoE application for priority 3 on eth2
	      lldptool -T -i eth2 -V APP -d app=3,1,35078

       Display locally configured application table on eth2
	      lldptool -t -i eth2 -V APP -c app

       Display last transmitted APP TLV on eth2
	      lldptool -t -i eth2 -V APP

SOURCE

       o      IEEE 802.1Qaz (http://www.ieee802.org/1/pages/dcbridges.html)

SEE ALSO

       lldptool(8), lldpad(8)

AUTHOR

       John Fastabend

open-lldp							   February 2010						       lldptool(8)