1. 28 6月, 2008 1 次提交
  2. 01 2月, 2008 2 次提交
    • P
      [NET_SCHED]: Add flow classifier · e5dfb815
      Patrick McHardy 提交于
      Add new "flow" classifier, which is meant to extend the SFQ hashing
      capabilities without hard-coding new hash functions and also allows
      deterministic mappings of keys to classes, replacing some out of tree
      iptables patches like IPCLASSIFY (maps IPs to classes), IPMARK (maps
      IPs to marks, with fw filters to classes), ...
      
      Some examples:
      
      - Classic SFQ hash:
      
        tc filter add ... flow hash \
        	keys src,dst,proto,proto-src,proto-dst divisor 1024
      
      - Classic SFQ hash, but using information from conntrack to work properly in
        combination with NAT:
      
        tc filter add ... flow hash \
        	keys nfct-src,nfct-dst,proto,nfct-proto-src,nfct-proto-dst divisor 1024
      
      - Map destination IPs of 192.168.0.0/24 to classids 1-257:
      
        tc filter add ... flow map \
        	key dst addend -192.168.0.0 divisor 256
      
      - alternatively:
      
        tc filter add ... flow map \
        	key dst and 0xff
      
      - similar, but reverse ordered:
      
        tc filter add ... flow map \
        	key dst and 0xff xor 0xff
      
      Perturbation is currently not supported because we can't reliable kill the
      timer on destruction.
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e5dfb815
    • P
      [NET_SCHED]: sch_ingress: remove netfilter support · 72eb7bd2
      Patrick McHardy 提交于
      Since the old policer code is gone, TC actions are needed for policing.
      The ingress qdisc can get packets directly from netif_receive_skb()
      in case TC actions are enabled or through netfilter otherwise, but
      since without TC actions there is no policer the only thing it actually
      does is count packets.
      
      Remove the netfilter support and always require TC actions.
      Signed-off-by: NPatrick McHardy <kaber@trash.net>
      Acked-by: NJamal Hadi Salim <hadi@cyberus.ca>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      72eb7bd2
  3. 29 1月, 2008 3 次提交
  4. 19 10月, 2007 1 次提交
  5. 11 10月, 2007 1 次提交
    • H
      [PKT_SCHED]: Add stateless NAT · b4219952
      Herbert Xu 提交于
      Stateless NAT is useful in controlled environments where restrictions are
      placed on through traffic such that we don't need connection tracking to
      correctly NAT protocol-specific data.
      
      In particular, this is of interest when the number of flows or the number
      of addresses being NATed is large, or if connection tracking information
      has to be replicated and where it is not practical to do so.
      
      Previously we had stateless NAT functionality which was integrated into
      the IPv4 routing subsystem.  This was a great solution as long as the NAT
      worked on a subnet to subnet basis such that the number of NAT rules was
      relatively small.  The reason is that for SNAT the routing based system
      had to perform a linear scan through the rules.
      
      If the number of rules is large then major renovations would have take
      place in the routing subsystem to make this practical.
      
      For the time being, the least intrusive way of achieving this is to use
      the u32 classifier written by Alexey Kuznetsov along with the actions
      infrastructure implemented by Jamal Hadi Salim.
      
      The following patch is an attempt at this problem by creating a new nat
      action that can be invoked from u32 hash tables which would allow large
      number of stateless NAT rules that can be used/updated in constant time.
      
      The actual NAT code is mostly based on the previous stateless NAT code
      written by Alexey.  In future we might be able to utilise the protocol
      NAT code from netfilter to improve support for other protocols.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b4219952
  6. 18 7月, 2007 1 次提交
  7. 15 7月, 2007 1 次提交
  8. 11 7月, 2007 2 次提交
  9. 26 4月, 2007 1 次提交
  10. 03 12月, 2006 2 次提交
  11. 01 7月, 2006 1 次提交
  12. 21 3月, 2006 1 次提交
  13. 14 1月, 2006 1 次提交
  14. 12 1月, 2006 1 次提交
  15. 18 11月, 2005 1 次提交
    • R
      [NET]: Sanitize NET_SCHED protection in /net/sched/Kconfig · 05b8b0fa
      Roman Zippel 提交于
      On Thu, 17 Nov 2005, David Gómez wrote:
      
      > I found out that if i select NET_CLS_ROUTE4, save my changes and exit
      > menuconfig, execute again make menuconfig and go to QoS options, then the new
      > available options are visible. So menuconfig has some problem refreshing
      > contents :?
      
      No, they were there before too, but you have to go up one level to see 
      them.
      
      It's better in 2.6.15-rc1-git5, but the menu structure is still a little 
      messed up, the patch below properly indents all menu entries.
      Signed-off-by: NRoman Zippel <zippel@linux-m68k.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      05b8b0fa
  16. 03 11月, 2005 1 次提交
  17. 14 10月, 2005 1 次提交
  18. 30 8月, 2005 1 次提交
  19. 12 7月, 2005 1 次提交
    • S
      [NET]: move config options out to individual protocols · 6a2e9b73
      Sam Ravnborg 提交于
      Move the protocol specific config options out to the specific protocols.
      With this change net/Kconfig now starts to become readable and serve as a
      good basis for further re-structuring.
      
      The menu structure is left almost intact, except that indention is
      fixed in most cases. Most visible are the INET changes where several
      "depends on INET" are replaced with a single ifdef INET / endif pair.
      
      Several new files were created to accomplish this change - they are
      small but serve the purpose that config options are now distributed
      out where they belongs.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6a2e9b73
  20. 25 6月, 2005 1 次提交
  21. 24 6月, 2005 2 次提交
  22. 09 6月, 2005 1 次提交
  23. 04 5月, 2005 1 次提交
  24. 25 4月, 2005 1 次提交
  25. 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