1. 21 3月, 2006 2 次提交
    • B
      [NET]: use fget_light() in net/socket.c · 6cb153ca
      Benjamin LaHaise 提交于
      Here's an updated copy of the patch to use fget_light in net/socket.c.
      Rerunning the tests show a drop of ~80Mbit/s on average, which looks
      bad until you see the drop in cpu usage from ~89% to ~82%.  That will
      get fixed in another patch...
      
      Before: max 8113.70, min 8026.32, avg 8072.34
       87380  16384  16384    10.01      8045.55   87.11    87.11    1.774   1.774
       87380  16384  16384    10.01      8065.14   90.86    90.86    1.846   1.846
       87380  16384  16384    10.00      8077.76   89.85    89.85    1.822   1.822
       87380  16384  16384    10.00      8026.32   89.80    89.80    1.833   1.833
       87380  16384  16384    10.01      8108.59   89.81    89.81    1.815   1.815
       87380  16384  16384    10.01      8034.53   89.01    89.01    1.815   1.815
       87380  16384  16384    10.00      8113.70   90.45    90.45    1.827   1.827
       87380  16384  16384    10.00      8111.37   89.90    89.90    1.816   1.816
       87380  16384  16384    10.01      8077.75   87.96    87.96    1.784   1.784
       87380  16384  16384    10.00      8062.70   90.25    90.25    1.834   1.834
      
      After: max 8035.81, min 7963.69, avg 7998.14
       87380  16384  16384    10.01      8000.93   82.11    82.11    1.682   1.682
       87380  16384  16384    10.01      8016.17   83.67    83.67    1.710   1.710
       87380  16384  16384    10.01      7963.69   83.47    83.47    1.717   1.717
       87380  16384  16384    10.01      8014.35   81.71    81.71    1.671   1.671
       87380  16384  16384    10.00      7967.68   83.41    83.41    1.715   1.715
       87380  16384  16384    10.00      7995.22   81.00    81.00    1.660   1.660
       87380  16384  16384    10.00      8002.61   83.90    83.90    1.718   1.718
       87380  16384  16384    10.00      8035.81   81.71    81.71    1.666   1.666
       87380  16384  16384    10.01      8005.36   82.56    82.56    1.690   1.690
       87380  16384  16384    10.00      7979.61   82.50    82.50    1.694   1.694
      Signed-off-by: NBenjamin LaHaise <bcrl@linux.intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6cb153ca
    • D
      [NET]: Do not lose accepted socket when -ENFILE/-EMFILE. · 39d8c1b6
      David S. Miller 提交于
      Try to allocate the struct file and an unused file
      descriptor before we try to pull a newly accepted
      socket out of the protocol layer.
      
      Based upon a patch by Prassana Meda.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      39d8c1b6
  2. 06 2月, 2006 1 次提交
  3. 31 1月, 2006 1 次提交
  4. 12 1月, 2006 1 次提交
  5. 04 1月, 2006 4 次提交
  6. 28 9月, 2005 1 次提交
    • F
      [NET]: Fix module reference counts for loadable protocol modules · a79af59e
      Frank Filz 提交于
      I have been experimenting with loadable protocol modules, and ran into
      several issues with module reference counting.
      
      The first issue was that __module_get failed at the BUG_ON check at
      the top of the routine (checking that my module reference count was
      not zero) when I created the first socket. When sk_alloc() is called,
      my module reference count was still 0. When I looked at why sctp
      didn't have this problem, I discovered that sctp creates a control
      socket during module init (when the module ref count is not 0), which
      keeps the reference count non-zero. This section has been updated to
      address the point Stephen raised about checking the return value of
      try_module_get().
      
      The next problem arose when my socket init routine returned an error.
      This resulted in my module reference count being decremented below 0.
      My socket ops->release routine was also being called. The issue here
      is that sock_release() calls the ops->release routine and decrements
      the ref count if sock->ops is not NULL. Since the socket probably
      didn't get correctly initialized, this should not be done, so we will
      set sock->ops to NULL because we will not call try_module_get().
      
      While searching for another bug, I also noticed that sys_accept() has
      a possibility of doing a module_put() when it did not do an
      __module_get so I re-ordered the call to security_socket_accept().
      Signed-off-by: NFrank Filz <ffilzlnx@us.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a79af59e
  7. 27 9月, 2005 1 次提交
  8. 17 9月, 2005 1 次提交
  9. 08 9月, 2005 1 次提交
  10. 07 9月, 2005 1 次提交
  11. 30 8月, 2005 3 次提交
  12. 23 6月, 2005 1 次提交
  13. 02 6月, 2005 1 次提交
  14. 17 5月, 2005 1 次提交
  15. 06 5月, 2005 1 次提交
  16. 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