1. 23 8月, 2012 1 次提交
  2. 02 7月, 2012 5 次提交
  3. 28 6月, 2012 4 次提交
  4. 25 6月, 2012 1 次提交
  5. 21 6月, 2012 9 次提交
  6. 19 6月, 2012 1 次提交
  7. 11 5月, 2012 1 次提交
  8. 11 4月, 2012 3 次提交
  9. 17 2月, 2012 2 次提交
  10. 30 5月, 2011 5 次提交
  11. 08 5月, 2011 1 次提交
  12. 31 1月, 2011 2 次提交
  13. 17 12月, 2010 1 次提交
  14. 30 11月, 2010 3 次提交
    • M
      Staging: batman-adv: adding gateway functionality · dfaf9dd3
      Marek Lindner 提交于
      Via the /sys filesystem you can change the gateway mode of a node using
      gw_mode. Adjustments to it can be done using gw_bandwidth for server
      mode and gw_sel_class for client mode.
      Signed-off-by: NMarek Lindner <lindner_marek@yahoo.de>
      [sven.eckelmann@gmx.de: Rework on top of current version]
      Signed-off-by: NSven Eckelmann <sven.eckelmann@gmx.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      dfaf9dd3
    • S
      Staging: batman-adv: Limit spin_locks to spin_lock_bh · 7a18deb7
      Sven Eckelmann 提交于
      spin_lock_irqsave disables the IRQs and stores them inside the flags
      provided by the caller. This is needed to protect a bottom half handler
      or a user context critical section from being interrupted by an
      interrupt handler which also tries to acquire the spinlock and locks
      forever.
      
      The linux device drivers will receive the packets inside an interrupt
      handler and the network infrastructure will process them inside bottom
      half. Thus batman-adv will only run in user context and bottom half
      handlers. We can conclude that batman-adv doesn't share its own
      spinlocks with real interrupt handlers.
      
      This makes it possible to exchange the quite complex spin_lock_irqsave
      with spin_lock_bh which only stops bottom halves from running on the
      current cpu, but allows interrupt handlers to take over to keep the
      interrupt latency low.
      Signed-off-by: NSven Eckelmann <sven.eckelmann@gmx.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      7a18deb7
    • M
      Staging: batman-adv: softif bridge loop avoidance · 42019357
      Marek Lindner 提交于
      By connecting multiple batman-adv mesh nodes to the same ethernet
      segment a loop can be created when the soft-interface is bridged
      into that ethernet segment. A simple visualization of the loop
      involving the most common case - a LAN as ethernet segment:
      
      node1  <-- LAN  -->  node2
         |                   |
       wifi  <-- mesh -->  wifi
      
      Packets from the LAN (e.g. ARP broadcasts) will circle forever from
      node1 or node2 over the mesh back into the LAN.
      
      This patch adds the functionality to detect other batman-adv nodes
      connected to the LAN and select a 'gateway' to talk to the
      non-batman-adv devices on this LAN. All traffic from and to the mesh
      will be handled by this gateway to avoid the loop. OGMs received via
      the soft-interface are interpreted as 'port announcements' to locate
      potential batman-adv nodes. The patch can also deal with vlans on
      top of batX and offers a list of LAN neighbors via debugfs.
      Signed-off-by: NMarek Lindner <lindner_marek@yahoo.de>
      [sven.eckelmann@gmx.de: Rework on top of current version]
      Signed-off-by: NSven Eckelmann <sven.eckelmann@gmx.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      42019357
  15. 21 9月, 2010 1 次提交