1. 22 8月, 2011 2 次提交
  2. 13 7月, 2011 1 次提交
  3. 05 7月, 2011 1 次提交
  4. 20 6月, 2011 5 次提交
    • A
      batman-adv: improved gateway tq-based selection · 43676ab5
      Antonio Quartulli 提交于
      If a client issues a DHCPREQUEST for renewal, the packet is dropped
      if the old destination (the old gateway for the client) TQ is smaller
      than the current best gateway TQ less GW_THRESHOLD
      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>
      43676ab5
    • A
      batman-adv: improved roaming mechanism · cc47f66e
      Antonio Quartulli 提交于
      With the current client announcement implementation, in case of roaming,
      an update is triggered on the new AP serving the client. At that point
      the new information is spread around by means of the OGM broadcasting
      mechanism. Until this operations is not executed, no node is able to
      correctly route traffic towards the client. This obviously causes packet
      drops and introduces a delay in the time needed by the client to recover
      its connections.
      
      A new packet type called ROAMING_ADVERTISEMENT is added to account this
      issue.
      
      This message is sent in case of roaming from the new AP serving the
      client to the old one and will contain the client MAC address. In this
      way an out-of-OGM update is immediately committed, so that the old node
      can update its global translation table. Traffic reaching this node will
      then be redirected to the correct destination utilising the fresher
      information. Thus reducing the packet drops and the connection recovery
      delay.
      Signed-off-by: NAntonio Quartulli <ordex@autistici.org>
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      cc47f66e
    • 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
    • S
      batman-adv: Reduce usage of char · b4e17054
      Sven Eckelmann 提交于
      char was used in different places to store information without really
      using the characteristics of that data type or by ignoring the fact that
      char has not a well defined signedness.
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      b4e17054
    • S
      batman-adv: Keep interface_tx as local function · db69ecfc
      Sven Eckelmann 提交于
      interface_tx is not used outside of soft-interface.c and thus doesn't
      need to be declared inside soft-interface.h
      Signed-off-by: NSven Eckelmann <sven@narfation.org>
      db69ecfc
  5. 30 5月, 2011 3 次提交
  6. 08 5月, 2011 5 次提交
  7. 02 5月, 2011 1 次提交
  8. 30 4月, 2011 1 次提交
    • D
      ethtool: cosmetic: Use ethtool ethtool_cmd_speed API · 70739497
      David Decotigny 提交于
      This updates the network drivers so that they don't access the
      ethtool_cmd::speed field directly, but use ethtool_cmd_speed()
      instead.
      
      For most of the drivers, these changes are purely cosmetic and don't
      fix any problem, such as for those 1GbE/10GbE drivers that indirectly
      call their own ethtool get_settings()/mii_ethtool_gset(). The changes
      are meant to enforce code consistency and provide robustness with
      future larger throughputs, at the expense of a few CPU cycles for each
      ethtool operation.
      
      All drivers compiled with make allyesconfig ion x86_64 have been
      updated.
      
      Tested: make allyesconfig on x86_64 + e1000e/bnx2x work
      Signed-off-by: NDavid Decotigny <decot@google.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      70739497
  9. 20 4月, 2011 1 次提交
  10. 18 4月, 2011 2 次提交
  11. 31 3月, 2011 1 次提交
  12. 05 3月, 2011 6 次提交
  13. 15 2月, 2011 1 次提交
  14. 12 2月, 2011 1 次提交
  15. 31 1月, 2011 1 次提交
  16. 17 12月, 2010 1 次提交
  17. 30 11月, 2010 7 次提交
    • S
      Staging: batman-adv: Use kernel functions to identify broadcasts · 951c44e0
      Sven Eckelmann 提交于
      linux/etherdevice.h already provides functions to classify different
      ethernet addresses. These inlineable functions should be used instead of
      custom functions.
      
      The check for multicast together with multicast can also be replaced
      with a single test for multicast because for every ethernet address x
      following is always true:
      
      is_broadcast_ether_addr(x) => is_multicast_ether_addr(x)
      
      or when looking more at the implementation:
      
      (FF:FF:FF:FF:FF:FF == x) => [(01:00:00:00:00:00 & x) != 00:00:00:00:00:00]
      Reported-by: NTobias Klauser <tklauser@distanz.ch>
      Signed-off-by: NSven Eckelmann <sven.eckelmann@gmx.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      951c44e0
    • M
      Staging: batman-adv: send DHCP requests directly to the chosen gw · 6c3a42db
      Marek Lindner 提交于
      If the gateway client mode is active batman-adv will send the
      broadcasted DHCP requests via unicast to the currently selected best
      gateway. Therefore attached clients can profit from batman's knowledge
      about the network topology.
      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>
      6c3a42db
    • 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
    • L
      Staging: batman-adv: Make hop_penalty configurable via sysfs · 1341a00a
      Linus Lüssing 提交于
      When having a mixed topology of both very mobile and rather static
      nodes, you are usually best advised to set the originator interval on
      all nodes to a level best suited for the most mobile node.
      
      However, if most of the nodes are rather static, this can create a lot
      of undesired overhead as a trade-off then. If setting the interval too
      low on the static nodes, a mobile node might be chosen as a router for
      too long, not switching away from it fast enough because of its
      mobility and the low frequency of ogms of static nodes.
      
      Exposing the hop_penalty is especially useful for the stated scenario: A
      static node can keep the default originator interval, a mobile node can
      select a quicker one resulting in faster route updates towards this
      mobile node. Additionally, such a mobile node could select a higher hop
      penalty (or even set it to 255 to disable acting as a router for other
      nodes) to make it less desirable, letting other nodes avoid selecting
      this mobile node as a router.
      Signed-off-by: NLinus Lüssing <linus.luessing@ascom.ch>
      Signed-off-by: NSven Eckelmann <sven.eckelmann@gmx.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      1341a00a
    • L
      Staging: batman-adv: Unify sysfs file names with their bat_priv atomics · 641ee3f8
      Linus Lüssing 提交于
      Both sysfs entries and variable names shall be as descriptive as
      possible while not exceeding a certain length. This patch renames
      bat_priv atomics to be equally descriptive with their according sysfs
      entries.
      
      Unifying sysfs and bat_priv atomic names also makes it easier to find
      each others pendant.
      
      The reduced ("type"-)information which was previously indicated with a
      _enabled for booleans got substituted by a comment in bat_priv.
      
      This patch has also been done in regards for the future BAT_ATTR_*
      macros (they only need one name argument instead of a file and variable
      name).
      Signed-off-by: NLinus Lüssing <linus.luessing@web.de>
      Signed-off-by: NMarek Lindner <lindner_marek@yahoo.de>
      Signed-off-by: NSven Eckelmann <sven.eckelmann@gmx.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      641ee3f8
    • 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