February 2014 Archives by thread

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...

Starting: Wed Feb 5 04:55:40 UTC 2014
Ending: Fri Feb 28 19:58:57 UTC 2014
Messages: 93

• Malloc alignment in libstand / loader(8)   Ian Lepore
  • Malloc alignment in libstand / loader(8)   John Baldwin
    • Malloc alignment in libstand / loader(8)   Ian Lepore
      • Malloc alignment in libstand / loader(8)   John Baldwin
    • Malloc alignment in libstand / loader(8)   Warner Losh
• mbuf and uio   Luca Ferrari
  • mbuf and uio   Alfred Perlstein
    • mbuf and uio   John Baldwin
      • mbuf and uio   Luca Ferrari
• flowtable, collisions, locking and CPU affinity   Adrian Chadd
  • flowtable, collisions, locking and CPU affinity   Ryan Stone
    • flowtable, collisions, locking and CPU affinity   John-Mark Gurney
    • flowtable, collisions, locking and CPU affinity   Adrian Chadd
• CFR: unifing sha256 userland/kernel implementation...   John-Mark Gurney
  • CFR: unifing sha256 userland/kernel implementation...   John-Mark Gurney
    • CFR: unifing sha256 userland/kernel implementation...   Pawel Jakub Dawidek
• core dump vs kern.ipc.shm_use_phys   John Baldwin
• [flowtable] don't insert a flowtable entry if the lle isn't yet valid   Adrian Chadd
• Automatic enabling of serial console   Michael Dexter
  • Automatic enabling of serial console   Peter Grehan
• can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Adrian Chadd
  • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Ryan Stone
    • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Adrian Chadd
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Adrian Chadd
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   John Baldwin
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Adrian Chadd
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   John Baldwin
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Andrey Chernov
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   John Baldwin
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Andrey Chernov
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Andrey Chernov
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Andriy Gapon
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   John-Mark Gurney
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Andrey Chernov
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   John Baldwin
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Andrey Chernov
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Andrey Chernov
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Adrian Chadd
      • can the scheduler decide to schedule an interrupted but runnable thread on another CPU core? What are the implications for code?   Adrian Chadd
• [rfc] bind per-cpu timeout threads to each CPU   Adrian Chadd
  • [rfc] bind per-cpu timeout threads to each CPU   Alexander Motin
    • [rfc] bind per-cpu timeout threads to each CPU   Adrian Chadd
      • [rfc] bind per-cpu timeout threads to each CPU   Alexander Motin
      • [rfc] bind per-cpu timeout threads to each CPU   Adrian Chadd
      • [rfc] bind per-cpu timeout threads to each CPU   Alexander Motin
      • [rfc] bind per-cpu timeout threads to each CPU   Slawa Olhovchenkov
      • [rfc] bind per-cpu timeout threads to each CPU   Alexander Motin
      • [rfc] bind per-cpu timeout threads to each CPU   Jeffrey Carl Faden
      • [rfc] bind per-cpu timeout threads to each CPU   Adrian Chadd
      • [rfc] bind per-cpu timeout threads to each CPU   Slawa Olhovchenkov
      • [rfc] bind per-cpu timeout threads to each CPU   John Baldwin
      • [rfc] bind per-cpu timeout threads to each CPU   John Baldwin
      • [rfc] bind per-cpu timeout threads to each CPU   Adrian Chadd
• [rfc] add callgraph PC annotation to pmcstat   Adrian Chadd
  • [rfc] add callgraph PC annotation to pmcstat   Adrian Chadd
• terminfo   Bryan Drewery
  • terminfo   Ed Schouten
    • terminfo   Ian Lepore
      • terminfo   Bruce Evans
      • terminfo   John-Mark Gurney
      • terminfo   Ian Lepore
      • terminfo   Bruce Evans
      • terminfo   Warner Losh
      • terminfo   Dag-Erling Smørgrav
      • terminfo   Bob Bishop
      • terminfo   Joel Dahl
      • terminfo   Slawa Olhovchenkov
      • terminfo   Kim Shrier
      • terminfo   olli hauer
      • terminfo   Ed Schouten
    • terminfo   Thomas Dickey
      • terminfo   Ed Schouten
      • terminfo   Andrey Chernov
      • terminfo   Ed Schouten
      • terminfo   Andrey Chernov
      • terminfo   Thomas Dickey
      • terminfo   Peter Jeremy
      • terminfo   Jilles Tjoelker
  • terminfo   Peter Wemm
    • terminfo   Bruce Evans
    • terminfo   Thomas Dickey
      • terminfo   Thomas Dickey
      • terminfo   Thomas Dickey
• small kernel kernel option...   John-Mark Gurney
  • small kernel kernel option...   Warner Losh
  • small kernel kernel option...   Luigi Rizzo
    • small kernel kernel option...   John-Mark Gurney
      • small kernel kernel option...   Adrian Chadd
      • small kernel kernel option...   Warner Losh
  • small kernel kernel option...   Julian Elischer
  • small kernel kernel option...   Peter Jeremy
    • small kernel kernel option...   John-Mark Gurney
• No subject   Grazia Valentino

Last message date: Fri Feb 28 19:58:57 UTC 2014
Archived on: Fri Feb 28 19:59:03 UTC 2014

• Messages sorted by: [ subject ] [ author ] [ date ]
• More info on this list...