Skip to content

K
Kernel

openeuler / Kernel
大约 1 年 前同步成功

通知 5
Star 0
Fork 0
K
Kernel

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 29 10月, 2012 1 次提交
  3. 02 7月, 2012 7 次提交
  5. 28 6月, 2012 5 次提交
  7. 25 6月, 2012 3 次提交
  9. 21 6月, 2012 5 次提交
  11. 19 6月, 2012 2 次提交
  13. 11 5月, 2012 2 次提交
  15. 16 4月, 2012 1 次提交
  17. 11 4月, 2012 3 次提交
  19. 11 3月, 2012 1 次提交
  21. 28 2月, 2012 1 次提交
  23. 17 2月, 2012 2 次提交
  25. 20 11月, 2011 1 次提交
  27. 22 8月, 2011 1 次提交
  29. 20 6月, 2011 2 次提交
    • A
      batman-adv: add wrapper function to throw uevent in userspace · c6bda689
      由 Antonio Quartulli 提交于 
      Using throw_uevent() is now possible to trigger uevent signal that can
be recognised in userspace. Uevents will be triggered through the
/devices/virtual/net/{MESH_IFACE} kobject.

A triggered uevent has three properties:
- type: the event class. Who generates the event (only 'gw' is currently
  defined). Corresponds to the BATTYPE uevent variable.
- action: the associated action with the event ('add'/'change'/'del' are
  currently defined). Corresponds to the BATACTION uevent variable.
- data: any useful data for the userspace. Corresponds to the BATDATA
  uevent variable.
Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
Signed-off-by: NSven Eckelmann <sven@narfation.org>
      c6bda689
    • A
      batman-adv: improved client announcement mechanism · a73105b8
      由 Antonio Quartulli 提交于 
      The client announcement mechanism informs every mesh node in the network
of any connected non-mesh client, in order to find the path towards that
client from any given point in the mesh.

The old implementation was based on the simple idea of appending a data
buffer to each OGM containing all the client MAC addresses the node is
serving. All other nodes can populate their global translation tables
(table which links client MAC addresses to node addresses) using this
MAC address buffer and linking it to the node's address contained in the
OGM. A node that wants to contact a client has to lookup the node the
client is connected to and its address in the global translation table.

It is easy to understand that this implementation suffers from several
issues:
 - big overhead (each and every OGM contains the entire list of
   connected clients)
 - high latencies for client route updates due to long OGM trip time and
   OGM losses

The new implementation addresses these issues by appending client
changes (new client joined or a client left) to the OGM instead of
filling it with all the client addresses each time. In this way nodes
can modify their global tables by means of "updates", thus reducing the
overhead within the OGMs.

To keep the entire network in sync each node maintains a translation
table version number (ttvn) and a translation table checksum. These
values are spread with the OGM to allow all the network participants to
determine whether or not they need to update their translation table
information.

When a translation table lookup is performed in order to send a packet
to a client attached to another node, the destination's ttvn is added to
the payload packet. Forwarding nodes can compare the packet's ttvn with
their destination's ttvn (this node could have a fresher information
than the source) and re-route the packet if necessary. This greatly
reduces the packet loss of clients roaming from one AP to the next.
Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
Signed-off-by: NMarek Lindner <lindner_marek@yahoo.de>
Signed-off-by: NSven Eckelmann <sven@narfation.org>
      a73105b8
  31. 10 6月, 2011 1 次提交
  33. 30 5月, 2011 1 次提交
  35. 08 5月, 2011 1 次提交
    • S
      batman-adv: Avoid deadlock between rtnl_lock and s_active · 3a4375a9
      由 Sven Eckelmann 提交于 
      The hard_if_event is called by the notifier with rtnl_lock and tries to
remove sysfs entries when a NETDEV_UNREGISTER event is received. This
will automatically take the s_active lock.

The s_active lock is also used when a new interface is added to a meshif
through sysfs. In that situation we cannot wait for the rntl_lock before
creating the actual batman-adv interface to prevent a deadlock. It is
still possible to try to get the rtnl_lock and immediately abort the
current operation when the trylock call failed.
Signed-off-by: NSven Eckelmann <sven@narfation.org>
      3a4375a9