1. 20 10月, 2007 1 次提交
    • M
      Change struct marker users · 1c3f0b8e
      Mathieu Desnoyers 提交于
      Prior to use struct marker in the linux kernel markers, we need to clean
      two drivers which use this structure name.
      
      Change bonding driver types :
      - struct marker to struct bond_marker.
      - marker_t to bond_marker_t.
      - marker_header to bond_marker_header.
      - marker_header_t to bond_marker_header_t.
      
      Change qla4xxx struct marker_entry usage :
      - Change struct marker_entry for struct qla4_marker_entry.
      Signed-off-by: NMathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
      Cc: Chad Tindel <ctindel@users.sourceforge.net>
      Cc: Jay Vosburgh <fubar@us.ibm.com>
      Cc: David Somayajulu <david.somayajulu@qlogic.com>
      Cc: James Bottomley <James.Bottomley@SteelEye.com>
      Cc: Ravi Anand <ravi.anand@qlogic.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      1c3f0b8e
  2. 11 10月, 2007 2 次提交
  3. 21 6月, 2007 1 次提交
    • J
      bonding: Fix 802.3ad no carrier on "no partner found" instance · 031ae4de
      Jay Vosburgh 提交于
      	Modify carrier state determination for 802.3ad mode to comply
      with section 43.3.9 of IEEE 802.3, which requires that "Links that are
      not successful candidates for aggregation (e.g., links that are attached
      to other devices that cannot perform aggregation or links that have been
      manually configured to be non-aggregatable) are enabled to operate as
      individual IEEE 802.3 links."
      
      	Bug reported by Laurent Chavey <chavey@google.com>.  This patch
      is an updated version of his patch that changes the wording of
      commentary and adds an update to the driver version.
      Signed-off-by: NJay Vosburgh <fubar@us.ibm.com>
      Signed-off-by: NLaurent Chavey <chavey@google.com>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      031ae4de
  4. 26 4月, 2007 3 次提交
  5. 26 9月, 2006 2 次提交
  6. 30 3月, 2006 1 次提交
  7. 29 11月, 2005 1 次提交
  8. 14 11月, 2005 1 次提交
  9. 30 8月, 2005 1 次提交
    • D
      [NET]: Kill skb->real_dev · f2ccd8fa
      David S. Miller 提交于
      Bonding just wants the device before the skb_bond()
      decapsulation occurs, so simply pass that original
      device into packet_type->func() as an argument.
      
      It remains to be seen whether we can use this same
      exact thing to get rid of skb->input_dev as well.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f2ccd8fa
  10. 27 6月, 2005 1 次提交
    • J
      bonding: xor/802.3ad improved slave hash · 169a3e66
      Jay Vosburgh 提交于
      Add support for alternate slave selection algorithms to bonding
      balance-xor and 802.3ad modes.  Default mode (what we have now: xor of
      MAC addresses) is "layer2", new choice is "layer3+4", using IP and port
      information for hashing to select peer.
      
      Originally submitted by Jason Gabler for balance-xor mode;
      modified by Jay Vosburgh to additionally support 802.3ad mode.  Jason's
      original comment is as follows:
      
      The attached patch to the Linux Etherchannel Bonding driver modifies the
      driver's "balance-xor" mode as follows:
      
            - alternate hashing policy support for mode 2
              * Added kernel parameter "xmit_policy" to allow the specification
                of different hashing policies for mode 2.  The original mode 2
                policy is the default, now found in xmit_hash_policy_layer2().
              * Added xmit_hash_policy_layer34()
      
      This patch was inspired by hashing policies implemented by Cisco,
      Foundry and IBM, which are explained in
      Foundry documentation found at:
      http://www.foundrynet.com/services/documentation/sribcg/Trunking.html#112750Signed-off-by: NJason Gabler <jygabler@lbl.gov>
      Signed-off-by: NJay Vosburgh <fubar@us.ibm.com>
      169a3e66
  11. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4