tech-kern by thread

• Date Index
• Date Index (newest page)
• Old Index

• GSoC Subfile Status Update, Adam Burkepile
  • Re: GSoC Subfile Status Update, Hubert Feyrer
    • Re: GSoC Subfile Status Update, Adam Burkepile
• rump ?, kamel derouiche
  • Re: rump ?, matthew sporleder
• Including pf/altq in GENERIC?, Adam Hoka
  • Re: Including pf/altq in GENERIC?, Thor Lancelot Simon
    • Re: Including pf/altq in GENERIC?, Adam Hoka
  • <Possible follow-ups>
  • Re: Including pf/altq in GENERIC?, Brian Buhrow
• Idea wanted; block disk on network (SC101T), Toru Nishimura
  • Re: Idea wanted; block disk on network (SC101T), Daniel Carosone
  • Re: Idea wanted; block disk on network (SC101T), Steven M. Bellovin
    • Re: Idea wanted; block disk on network (SC101T), Steven M. Bellovin
      • Re: Idea wanted; block disk on network (SC101T), Christoph Egger
      • Re: Idea wanted; block disk on network (SC101T), David Young
      • Re: Idea wanted; block disk on network (SC101T), Toru Nishimura
  • Re: Idea wanted; block disk on network (SC101T), der Mouse
• Xen 3.3: Problem HVM guest, Christoph Egger
  • Re: Xen 3.3: Problem HVM guest, Christoph Egger
    • Re: Xen 3.3: Problem HVM guest, Michael Litchard
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
    • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Manuel Bouyer
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
      • Re: Xen 3.3: Problem HVM guest, Matthias Scheler
      • Re: Xen 3.3: Problem HVM guest, Christoph Egger
• VOP_CREATE hanging, Adam Burkepile
  • Re: VOP_CREATE hanging, Antti Kantee
    • Re: VOP_CREATE hanging, David Holland
    • Re: VOP_CREATE hanging, Adam Burkepile
      • Re: VOP_CREATE hanging, Antti Kantee
      • Re: VOP_CREATE hanging, David Holland
• rfc: C99 style of the uintN_t types, Andy Shevchenko
  • Re: rfc: C99 style of the uintN_t types, Valeriy E. Ushakov
    • Re: rfc: C99 style of the uintN_t types, Andy Shevchenko
      • Re: rfc: C99 style of the uintN_t types, SODA Noriyuki
      • Re: rfc: C99 style of the uintN_t types, Jason Thorpe
      • Re: rfc: C99 style of the uintN_t types, Andy Shevchenko
      • Re: rfc: C99 style of the uintN_t types, James Chacon
      • Re: rfc: C99 style of the uintN_t types, Jason Thorpe
      • Re: rfc: C99 style of the uintN_t types, Peter Seebach
      • Re: rfc: C99 style of the uintN_t types, Bill Stouder-Studenmund
      • Re: rfc: C99 style of the uintN_t types, Eric Haszlakiewicz
    • Re: rfc: C99 style of the uintN_t types, Joerg Sonnenberger
    • Re: rfc: C99 style of the uintN_t types, Joerg Sonnenberger
  • Re: rfc: C99 style of the uintN_t types, Thor Lancelot Simon
    • Re: rfc: C99 style of the uintN_t types, Andy Shevchenko
      • Re: rfc: C99 style of the uintN_t types, Valeriy E. Ushakov
      • Re: rfc: C99 style of the uintN_t types, Andy Shevchenko
• VOP_WRITE without vnode lock, Juergen Hannken-Illjes
  • Re: VOP_WRITE without vnode lock, der Mouse
    • Re: VOP_WRITE without vnode lock, Juergen Hannken-Illjes
  • Re: VOP_WRITE without vnode lock, David Holland
• Odd stacksize problem, Adam Hoka
  • Re: Odd stacksize problem, Matthias Drochner
• Case insensitive FFS, Matthias Scheler
  • Re: Case insensitive FFS, Martin Husemann
    • Re: Case insensitive FFS, Matthias Scheler
      • Re: Case insensitive FFS, Takahiro Kambe
    • Re: Case insensitive FFS, Aleksey Cheusov
  • Re: Case insensitive FFS, Antti Kantee
    • Re: Case insensitive FFS, Matthias Scheler
  • Re: Case insensitive FFS, Greg Troxel
    • Re: Case insensitive FFS, SODA Noriyuki
    • Re: Case insensitive FFS, Matthias Scheler
      • Re: Case insensitive FFS, Greg Troxel
      • Re: Case insensitive FFS, Matthias Scheler
      • Re: Case insensitive FFS, Antti Kantee
      • Re: Case insensitive FFS, Bill Stouder-Studenmund
      • Re: Case insensitive FFS, Daniel Carosone
  • Re: Case insensitive FFS, der Mouse
• interrupts & pmf/legacy shutdown hooks (was Re: CV, David Young
  • Re: interrupts & pmf/legacy shutdown hooks (was Re, Matthias Drochner
    • Re: interrupts & pmf/legacy shutdown hooks (was Re, Simon Burge
      • Re: interrupts & pmf/legacy shutdown hooks (was Re, Matthias Drochner
• Large memory with netbsd 4, juanito
  • Re: Large memory with netbsd 4, Simon Burge
    • Re: Large memory with netbsd 4, Paul Goyette
      • Re: Large memory with netbsd 4, Manuel Bouyer
      • Re: Large memory with netbsd 4, Paul Goyette
      • Re: Large memory with netbsd 4, Manuel Bouyer
      • Re: Large memory with netbsd 4, Joerg Sonnenberger
      • Re: Large memory with netbsd 4, Paul Goyette
      • Re: Large memory with netbsd 4, Izumi Tsutsui
      • Re: Large memory with netbsd 4, Paul Goyette
    • Re: Large memory with netbsd 4, juanito
      • Re: Large memory with netbsd 4, Matthias Scheler
      • Re: Large memory with netbsd 4, Joerg Sonnenberger
      • Re: Large memory with netbsd 4, Steven M. Bellovin
  • Re: Large memory with netbsd 4, Greg A. Woods; Planix, Inc.
    • Re: Large memory with netbsd 4, David Holland
  • <Possible follow-ups>
  • Large memory with netbsd 4, Jean Praloran
  • Re: Large memory with netbsd 4, Brian Buhrow
• cpu_need_resched(t_vp->l_cpu, RESCHED_IMMED) for N, Bill Stouder-Studenmund
  • re: cpu_need_resched(t_vp->l_cpu, RESCHED_IMMED) f, matthew green
• VOP_ISLOCKED, Adam Burkepile
  • Re: VOP_ISLOCKED, Antti Kantee
• linux has added "close on exec" flags to lots of f, Perry E. Metzger
  • Re: linux has added "close on exec" flags to lots , Joerg Sonnenberger
    • Re: linux has added "close on exec" flags to lots , Perry E. Metzger
    • Re: linux has added "close on exec" flags to lots , Joerg Sonnenberger
      • Re: linux has added "close on exec" flags to lots , Love Hörnquist Åstrand
      • Re: linux has added "close on exec" flags to lots , Joerg Sonnenberger
      • Re: linux has added "close on exec" flags to lots , Perry E. Metzger
      • Re: linux has added "close on exec" flags to lots , Joerg Sonnenberger
      • Re: linux has added "close on exec" flags to lots , Love Hörnquist Åstrand
      • Re: linux has added "close on exec" flags to lots , Joerg Sonnenberger
      • Re: linux has added "close on exec" flags to lots , David Laight
      • Re: linux has added "close on exec" flags to lots , Steven M. Bellovin
      • Re: linux has added "close on exec" flags to lots , der Mouse
  • Re: linux has added "close on exec" flags to lots , Steven M. Bellovin
    • Re: linux has added "close on exec" flags to lots , Perry E. Metzger
    • Re: linux has added "close on exec" flags to lots , Joerg Sonnenberger
    • Re: linux has added "close on exec" flags to lots , Ignatios Souvatzis
• wpi0 related kernel crashes, Berndt Josef Wulf
  • Re: wpi0 related kernel crashes, Jared D. McNeill
  • Re: wpi0 related kernel crashes, Joerg Sonnenberger
    • Re: wpi0 related kernel crashes, Steven M. Bellovin
      • Re: wpi0 related kernel crashes, Joerg Sonnenberger
• rfc: POSIX conformance, Andy Shevchenko
  • Re: rfc: POSIX conformance, Andy Shevchenko
    • Re: rfc: POSIX conformance, Patrick Welche
      • Re: rfc: POSIX conformance, Andy Shevchenko
      • Re: rfc: POSIX conformance, Andy Shevchenko
      • Re: rfc: POSIX conformance, Christos Zoulas
      • Re: rfc: POSIX conformance, Christos Zoulas
      • Re: rfc: POSIX conformance, Peter Seebach
      • Re: rfc: POSIX conformance, Andy Shevchenko
      • Re: rfc: POSIX conformance, Peter Seebach
      • Re: rfc: POSIX conformance, Andy Shevchenko
      • Re: rfc: POSIX conformance, Andy Shevchenko
      • Re: rfc: POSIX conformance, Perry E. Metzger
      • Re: rfc: POSIX conformance, Matt Thomas
• WAPBL and backwards compatibility, Simon Burge
  • Re: WAPBL and backwards compatibility, Chris Gilbert
  • Re: WAPBL and backwards compatibility, Alan Barrett
    • Re: WAPBL and backwards compatibility, Martin Husemann
      • Re: WAPBL and backwards compatibility, Adam Hamsik
      • Re: WAPBL and backwards compatibility, David Maxwell
      • Re: WAPBL and backwards compatibility, Martin Husemann
    • Re: WAPBL and backwards compatibility, Bill Stouder-Studenmund
    • Re: WAPBL and backwards compatibility, Perry E. Metzger
      • Re: WAPBL and backwards compatibility, Bill Stouder-Studenmund
      • Re: WAPBL and backwards compatibility, Perry E. Metzger
  • Re: WAPBL and backwards compatibility, Michael Lorenz
  • Re: WAPBL and backwards compatibility, Thor Lancelot Simon
    • Re: WAPBL and backwards compatibility, Bill Stouder-Studenmund
    • Re: WAPBL and backwards compatibility, Jason Thorpe
  • Re: WAPBL and backwards compatibility, Greg A. Woods; Planix, Inc.
  • Re: WAPBL and backwards compatibility, Jason Thorpe
  • Re: WAPBL and backwards compatibility, Joerg Sonnenberger
  • Re: WAPBL and backwards compatibility, David Holland
  • Re: WAPBL and backwards compatibility, Manuel Bouyer