1. 11 12月, 2009 4 次提交
  2. 10 12月, 2009 2 次提交
  3. 09 12月, 2009 2 次提交
  4. 06 12月, 2009 1 次提交
    • D
      sparc: Set UTS_MACHINE correctly. · 7f5620a5
      David S. Miller 提交于
      "ARCH" can be just about anything, so we shouldn't end up
      with UTS_MACHINE of "sparc" in a 64-bit kernel build just
      because someone set the personality using 'sparc32' or
      similar.  CONFIG_SPARC64 drives the compilation and
      therefore provides the definitive value, not "ARCH".
      
      This mirrors commit 8c6531f7
      (x86: correctly set UTS_MACHINE for "make ARCH=x86")
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      7f5620a5
  5. 03 12月, 2009 3 次提交
  6. 28 11月, 2009 1 次提交
  7. 27 11月, 2009 1 次提交
  8. 26 11月, 2009 2 次提交
  9. 24 11月, 2009 1 次提交
    • D
      sparc64: Fix definition of VMEMMAP_SIZE. · bffbc94a
      David S. Miller 提交于
      This was the cause of various boot failures on V480, V880, etc.
      systems.
      
      Kernel image memory was being overwritten because the vmemmap[]
      array was being sized to small.  So if you had physical memory
      addresses past a certain point, the early bootup would spam
      all over variables in the kernel data section.
      
      The vmemmap mappings map page structs, not page struct pointers.
      And that was the key thinko in the macro definition.
      
      This was fixable thanks to the help, reports, and tireless patience
      of Hermann Lauer.
      Reported-by: NHermann Lauer <Hermann.Lauer@iwr.uni-heidelberg.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bffbc94a
  10. 18 11月, 2009 1 次提交
  11. 16 11月, 2009 3 次提交
  12. 09 11月, 2009 1 次提交
  13. 08 11月, 2009 2 次提交
  14. 07 11月, 2009 1 次提交
  15. 06 11月, 2009 2 次提交
  16. 03 11月, 2009 1 次提交
    • T
      sparc: Remove BKL from apc · 49ab972a
      Thomas Gleixner 提交于
      commit ab772027 (sparc: arch/sparc/kernel/apc.c to unlocked_ioctl)
      added lock/unlock_kernel() to the apc ioctl code.
      
      The code needs no serialization at all. Neither put/get_user nor the
      read/write access to the sbus devices require it. Remove BKL.
      
      cycle_kernel_lock() was added during the big BKL pushdown. It should
      ensure the serializiation against driver init code. In this case there
      is nothing to serialize. Remove it as well.
      Signed-off-by: NThomas Gleixner <tglx@linutronix.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      49ab972a
  17. 02 11月, 2009 1 次提交
  18. 16 10月, 2009 5 次提交
  19. 15 10月, 2009 1 次提交
  20. 13 10月, 2009 3 次提交
    • D
      sparc64: Set IRQF_DISABLED on LDC channel IRQs. · c58543c8
      David S. Miller 提交于
      With lots of virtual devices it's easy to generate a lot of
      events and chew up the kernel IRQ stack.
      Reported-by: Nhyl <heyongli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      c58543c8
    • A
      net: Introduce recvmmsg socket syscall · a2e27255
      Arnaldo Carvalho de Melo 提交于
      Meaning receive multiple messages, reducing the number of syscalls and
      net stack entry/exit operations.
      
      Next patches will introduce mechanisms where protocols that want to
      optimize this operation will provide an unlocked_recvmsg operation.
      
      This takes into account comments made by:
      
      . Paul Moore: sock_recvmsg is called only for the first datagram,
        sock_recvmsg_nosec is used for the rest.
      
      . Caitlin Bestler: recvmmsg now has a struct timespec timeout, that
        works in the same fashion as the ppoll one.
      
        If the underlying protocol returns a datagram with MSG_OOB set, this
        will make recvmmsg return right away with as many datagrams (+ the OOB
        one) it has received so far.
      
      . Rémi Denis-Courmont & Steven Whitehouse: If we receive N < vlen
        datagrams and then recvmsg returns an error, recvmmsg will return
        the successfully received datagrams, store the error and return it
        in the next call.
      
      This paves the way for a subsequent optimization, sk_prot->unlocked_recvmsg,
      where we will be able to acquire the lock only at batch start and end, not at
      every underlying recvmsg call.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a2e27255
    • N
      net: Generalize socket rx gap / receive queue overflow cmsg · 3b885787
      Neil Horman 提交于
      Create a new socket level option to report number of queue overflows
      
      Recently I augmented the AF_PACKET protocol to report the number of frames lost
      on the socket receive queue between any two enqueued frames.  This value was
      exported via a SOL_PACKET level cmsg.  AFter I completed that work it was
      requested that this feature be generalized so that any datagram oriented socket
      could make use of this option.  As such I've created this patch, It creates a
      new SOL_SOCKET level option called SO_RXQ_OVFL, which when enabled exports a
      SOL_SOCKET level cmsg that reports the nubmer of times the sk_receive_queue
      overflowed between any two given frames.  It also augments the AF_PACKET
      protocol to take advantage of this new feature (as it previously did not touch
      sk->sk_drops, which this patch uses to record the overflow count).  Tested
      successfully by me.
      
      Notes:
      
      1) Unlike my previous patch, this patch simply records the sk_drops value, which
      is not a number of drops between packets, but rather a total number of drops.
      Deltas must be computed in user space.
      
      2) While this patch currently works with datagram oriented protocols, it will
      also be accepted by non-datagram oriented protocols. I'm not sure if thats
      agreeable to everyone, but my argument in favor of doing so is that, for those
      protocols which aren't applicable to this option, sk_drops will always be zero,
      and reporting no drops on a receive queue that isn't used for those
      non-participating protocols seems reasonable to me.  This also saves us having
      to code in a per-protocol opt in mechanism.
      
      3) This applies cleanly to net-next assuming that commit
      97775007 (my af packet cmsg patch) is reverted
      Signed-off-by: NNeil Horman <nhorman@tuxdriver.com>
      Signed-off-by: NEric Dumazet <eric.dumazet@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      3b885787
  21. 12 10月, 2009 1 次提交
  22. 09 10月, 2009 1 次提交