From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Sat, 22 May 2010 06:53:15 +0800 MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="Boundary-00=_b7w9LI/SVPUxaHz" Message-Id: <201005220653.15929.lindner_marek@yahoo.de> Subject: [B.A.T.M.A.N.] sysfs & debugfs Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: The list for a Better Approach To Mobile Ad-hoc Networking --Boundary-00=_b7w9LI/SVPUxaHz Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, thanks to Sven's patches we made the transition to debugfs rather quickly. All batman tables (originator table / gateway table / translation tables) and the vis data output have been relocated to debugfs. Even the former batman device (used for layer2 icmp data) has been moved to debugfs which brings us an important step closer to the multiple mesh support. @Andrew: I attached the revised sysfs ABI files. Do you think it is feasible to get these last patches into 2.6.35 ? Cheers, Marek --Boundary-00=_b7w9LI/SVPUxaHz Content-Type: text/plain; charset="UTF-8"; name="sysfs-class-net-batman-adv" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="sysfs-class-net-batman-adv" What: /sys/class/net//batman-adv/mesh_iface Date: May 2010 Contact: Marek Lindner Description: The /sys/class/net//batman-adv/mesh_iface file displays the batman mesh interface this currently is associated with. What: /sys/class/net//batman-adv/iface_status Date: May 2010 Contact: Marek Lindner Description: Indicates the status of as it is seen by batman. --Boundary-00=_b7w9LI/SVPUxaHz Content-Type: text/plain; charset="UTF-8"; name="sysfs-class-net-mesh" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="sysfs-class-net-mesh" What: /sys/class/net//mesh/aggregated_ogms Date: May 2010 Contact: Marek Lindner Description: Indicates whether the batman protocol messages of the mesh shall be aggregated or not. What: /sys/class/net//mesh/orig_interval Date: May 2010 Contact: Marek Lindner Description: Defines the interval in milliseconds in which batman sends its protocol messages. What: /sys/class/net//mesh/vis_mode Date: May 2010 Contact: Marek Lindner Description: Each batman node only maintains information about its own local neighborhood, therefore generating graphs showing the topology of the entire mesh is not easily feasible without having a central instance to collect the local topologies from all nodes. This file allows to activate the collecting (server) mode. Once activated the topology can be retrieved by reading the vis_data file. --Boundary-00=_b7w9LI/SVPUxaHz--