1. 20 Mar, 2006 2 commits
  2. 19 Feb, 2006 1 commit
  3. 23 Jan, 2006 1 commit
  4. 09 Jan, 2006 1 commit
  5. 03 Jan, 2006 1 commit
    • Benjamin LaHaise's avatar
      [NET]: Speed up __alloc_skb() · 4947d3ef
      Benjamin LaHaise authored
      From: Benjamin LaHaise <bcrl@kvack.org>
      In __alloc_skb(), the use of skb_shinfo() which casts a u8 * to the 
      shared info structure results in gcc being forced to do a reload of the 
      pointer since it has no information on possible aliasing.  Fix this by 
      using a pointer to refer to skb_shared_info.
      By initializing skb_shared_info sequentially, the write combining buffers 
      can reduce the number of memory transactions to a single write.  Reorder 
      the initialization in __alloc_skb() to match the structure definition.  
      There is also an alignment issue on 64 bit systems with skb_shared_info 
      by converting nr_frags to a short everything packs up nicely.
      Also, pass the slab cache pointer according to the fclone flag instead 
      of using two almost identical function calls.
      This raises bw_unix performance up to a peak of 707KB/s when combined 
      with the spinlock patch.  It should help other networking protocols, too.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  6. 05 Dec, 2005 1 commit
  7. 09 Nov, 2005 1 commit
    • Yasuyuki Kozakai's avatar
      [NETFILTER]: Add nf_conntrack subsystem. · 9fb9cbb1
      Yasuyuki Kozakai authored
      The existing connection tracking subsystem in netfilter can only
      handle ipv4.  There were basically two choices present to add
      connection tracking support for ipv6.  We could either duplicate all
      of the ipv4 connection tracking code into an ipv6 counterpart, or (the
      choice taken by these patches) we could design a generic layer that
      could handle both ipv4 and ipv6 and thus requiring only one sub-protocol
      (TCP, UDP, etc.) connection tracking helper module to be written.
      In fact nf_conntrack is capable of working with any layer 3
      The existing ipv4 specific conntrack code could also not deal
      with the pecularities of doing connection tracking on ipv6,
      which is also cured here.  For example, these issues include:
      1) ICMPv6 handling, which is used for neighbour discovery in
         ipv6 thus some messages such as these should not participate
         in connection tracking since effectively they are like ARP
      2) fragmentation must be handled differently in ipv6, because
         the simplistic "defrag, connection track and NAT, refrag"
         (which the existing ipv4 connection tracking does) approach simply
         isn't feasible in ipv6
      3) ipv6 extension header parsing must occur at the correct spots
         before and after connection tracking decisions, and there were
         no provisions for this in the existing connection tracking
      4) ipv6 has no need for stateful NAT
      The ipv4 specific conntrack layer is kept around, until all of
      the ipv4 specific conntrack helpers are ported over to nf_conntrack
      and it is feature complete.  Once that occurs, the old conntrack
      stuff will get placed into the feature-removal-schedule and we will
      fully kill it off 6 months later.
      Signed-off-by: default avatarYasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
      Signed-off-by: default avatarHarald Welte <laforge@netfilter.org>
      Signed-off-by: default avatarArnaldo Carvalho de Melo <acme@mandriva.com>
  8. 28 Oct, 2005 1 commit
    • Ananda Raju's avatar
      [IPv4/IPv6]: UFO Scatter-gather approach · e89e9cf5
      Ananda Raju authored
      Attached is kernel patch for UDP Fragmentation Offload (UFO) feature.
      1. This patch incorporate the review comments by Jeff Garzik.
      2. Renamed USO as UFO (UDP Fragmentation Offload)
      3. udp sendfile support with UFO
      This patches uses scatter-gather feature of skb to generate large UDP
      datagram. Below is a "how-to" on changes required in network device
      driver to use the UFO interface.
      UDP Fragmentation Offload (UFO) Interface:
      UFO is a feature wherein the Linux kernel network stack will offload the
      IP fragmentation functionality of large UDP datagram to hardware. This
      will reduce the overhead of stack in fragmenting the large UDP datagram to
      MTU sized packets
      1) Drivers indicate their capability of UFO using
      dev->features |= NETIF_F_UFO | NETIF_F_HW_CSUM | NETIF_F_SG
      NETIF_F_HW_CSUM is required for UFO over ipv6.
      2) UFO packet will be submitted for transmission using driver xmit routine.
      UFO packet will have a non-zero value for
      skb_shinfo(skb)->ufo_size will indicate the length of data part in each IP
      fragment going out of the adapter after IP fragmentation by hardware.
      skb->data will contain MAC/IP/UDP header and skb_shinfo(skb)->frags[]
      contains the data payload. The skb->ip_summed will be set to CHECKSUM_HW
      indicating that hardware has to do checksum calculation. Hardware should
      compute the UDP checksum of complete datagram and also ip header checksum of
      each fragmented IP packet.
      For IPV6 the UFO provides the fragment identification-id in
      skb_shinfo(skb)->ip6_frag_id. The adapter should use this ID for generating
      IPv6 fragments.
      Signed-off-by: default avatarAnanda Raju <ananda.raju@neterion.com>
      Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (forwarded)
      Signed-off-by: default avatarArnaldo Carvalho de Melo <acme@mandriva.com>
  9. 25 Oct, 2005 1 commit
  10. 22 Oct, 2005 1 commit
  11. 08 Oct, 2005 1 commit
  12. 03 Oct, 2005 1 commit
    • Herbert Xu's avatar
      [NET]: Fix packet timestamping. · 325ed823
      Herbert Xu authored
      I've found the problem in general.  It affects any 64-bit
      architecture.  The problem occurs when you change the system time.
      Suppose that when you boot your system clock is forward by a day.
      This gets recorded down in skb_tv_base.  You then wind the clock back
      by a day.  From that point onwards the offset will be negative which
      essentially overflows the 32-bit variables they're stored in.
      In fact, why don't we just store the real time stamp in those 32-bit
      variables? After all, we're not going to overflow for quite a while
      When we do overflow, we'll need a better solution of course.
      Signed-off-by: default avatarHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  13. 29 Aug, 2005 8 commits
  14. 19 Jul, 2005 1 commit
  15. 08 Jul, 2005 1 commit
  16. 05 Jul, 2005 1 commit
  17. 23 Jun, 2005 2 commits
    • Thomas Graf's avatar
      [NET]: skb_find_text() - Find a text pattern in skb data · 3fc7e8a6
      Thomas Graf authored
      Finds a pattern in the skb data according to the specified
      textsearch configuration. Use textsearch_next() to retrieve
      subsequent occurrences of the pattern. Returns the offset
      to the first occurrence or UINT_MAX if no match was found.
      Signed-off-by: default avatarThomas Graf <tgraf@suug.ch>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Thomas Graf's avatar
      [NET]: Zerocopy sequential reading of skb data · 677e90ed
      Thomas Graf authored
      Implements sequential reading for both linear and non-linear
      skb data at zerocopy cost. The data is returned in chunks of
      arbitary length, therefore random access is not possible.
      	from	 := 0
      	to	 := 128
      	state	 := undef
      	data	 := undef
      	len	 := undef
      	consumed := 0
      	skb_prepare_seq_read(skb, from, to, &state)
      	while (len = skb_seq_read(consumed, &data, &state)) != 0 do
      		/* do something with 'data' of length 'len' */
      		if abort then
      			/* abort read if we don't wait for
      			 * skb_seq_read() to return 0 */
      		/* not necessary to consume all of 'len' */
      		consumed += len
      Signed-off-by: default avatarThomas Graf <tgraf@suug.ch>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  18. 21 Jun, 2005 1 commit
  19. 21 Apr, 2005 1 commit
  20. 19 Apr, 2005 2 commits
  21. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!