1. 28 9月, 2006 5 次提交
  2. 23 9月, 2006 1 次提交
  3. 14 9月, 2006 4 次提交
  4. 06 9月, 2006 1 次提交
  5. 30 8月, 2006 9 次提交
  6. 10 8月, 2006 1 次提交
  7. 04 8月, 2006 2 次提交
  8. 20 7月, 2006 1 次提交
  9. 18 7月, 2006 1 次提交
  10. 13 7月, 2006 4 次提交
  11. 09 7月, 2006 1 次提交
  12. 03 7月, 2006 1 次提交
  13. 01 7月, 2006 1 次提交
  14. 28 6月, 2006 1 次提交
  15. 23 6月, 2006 1 次提交
    • H
      [NET]: Merge TSO/UFO fields in sk_buff · 7967168c
      Herbert Xu 提交于
      Having separate fields in sk_buff for TSO/UFO (tso_size/ufo_size) is not
      going to scale if we add any more segmentation methods (e.g., DCCP).  So
      let's merge them.
      
      They were used to tell the protocol of a packet.  This function has been
      subsumed by the new gso_type field.  This is essentially a set of netdev
      feature bits (shifted by 16 bits) that are required to process a specific
      skb.  As such it's easy to tell whether a given device can process a GSO
      skb: you just have to and the gso_type field and the netdev's features
      field.
      
      I've made gso_type a conjunction.  The idea is that you have a base type
      (e.g., SKB_GSO_TCPV4) that can be modified further to support new features.
      For example, if we add a hardware TSO type that supports ECN, they would
      declare NETIF_F_TSO | NETIF_F_TSO_ECN.  All TSO packets with CWR set would
      have a gso_type of SKB_GSO_TCPV4 | SKB_GSO_TCPV4_ECN while all other TSO
      packets would be SKB_GSO_TCPV4.  This means that only the CWR packets need
      to be emulated in software.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7967168c
  16. 18 6月, 2006 1 次提交
  17. 14 6月, 2006 5 次提交