tech-kern by thread

• Date Index
• Old Index

• Kernel Single-user Memory usage breakdown results , Juha Keski-Saari
• ksyms_init considered too heavyweight for early bo, Martin Husemann
  • Re: ksyms_init considered too heavyweight for earl, Andrew Doran
  • Re: ksyms_init considered too heavyweight for earl, Michael
• interface detach/destroy hook?, der Mouse
  • Re: interface detach/destroy hook?, Joerg Sonnenberger
    • Re: interface detach/destroy hook?, der Mouse
      • Re: interface detach/destroy hook?, Martin Husemann
      • Re: interface detach/destroy hook?, der Mouse
      • Re: interface detach/destroy hook?, Joerg Sonnenberger
• Re: Using qsort(3) in the kernel, kamel derouiche
• Using qsort(3) in the kernel (was: CVS commit: src, Matthias Scheler
  • Re: Using qsort(3) in the kernel (was: CVS commit:, Andrew Doran
    • Re: Using qsort(3) in the kernel, Johnny Billquist
  • Re: Using qsort(3) in the kernel (was: CVS commit:, kamel derouiche
    • Re: Using qsort(3) in the kernel (was: CVS commit:, Steven M. Bellovin
      • Re: Using qsort(3) in the kernel (was: CVS commit:, Martin S. Weber
      • Re: Using qsort(3) in the kernel, Anders Magnusson
      • Re: Using qsort(3) in the kernel, Martin S. Weber
      • Re: Using qsort(3) in the kernel, David Holland
      • Re: Using qsort(3) in the kernel, David Laight
      • Re: Using qsort(3) in the kernel, Ignatios Souvatzis
      • Re: Using qsort(3) in the kernel, Johnny Billquist
      • Re: Using qsort(3) in the kernel, Johnny Billquist
      • Re: Using qsort(3) in the kernel, Steven M. Bellovin
      • Re: Using qsort(3) in the kernel, Johnny Billquist
      • Re: Using qsort(3) in the kernel, Matt Thomas
      • Re: Using qsort(3) in the kernel, Andrew Reilly
      • Re: Using qsort(3) in the kernel, Johnny Billquist
      • Re: Using qsort(3) in the kernel, Matt Thomas
      • Re: Using qsort(3) in the kernel, Johnny Billquist
  • Re: Using qsort(3) in the kernel (was: CVS commit:, Joerg Sonnenberger
    • Re: Using qsort(3) in the kernel (was: CVS commit:, Martin S. Weber
    • Re: Using qsort(3) in the kernel, Aleksey Cheusov
    • Re: Using qsort(3) in the kernel (was: CVS commit:, Andrew Doran
• options RND_COM considered dangeous, Rafal Boni
  • Re: options RND_COM considered dangeous, Daniel Carosone
    • Re: options RND_COM considered dangeous, Andrew Doran
• Re: Lastest WAPBL update destroys the root partiti, Michael
  • Re: Lastest WAPBL update destroys the root partiti, Joerg Sonnenberger
    • Re: Lastest WAPBL update destroys the root partiti, Michael
      • Re: Lastest WAPBL update destroys the root partiti, Joerg Sonnenberger
      • Re: Lastest WAPBL update destroys the root partiti, Michael
      • Re: Lastest WAPBL update destroys the root partiti, Joerg Sonnenberger
      • Re: Lastest WAPBL update destroys the root partiti, Michael
      • Re: Lastest WAPBL update destroys the root partiti, Joerg Sonnenberger
      • Re: Lastest WAPBL update destroys the root partiti, Michael
      • Re: Lastest WAPBL update destroys the root partiti, Michael
    • Re: Lastest WAPBL update destroys the root partiti, Bernd Ernesti
• RFC: generic notification mechanism, Christoph Egger
  • Re: RFC: generic notification mechanism, Antti Kantee
    • Re: RFC: generic notification mechanism, Christoph Egger
• TP4 over IP and EON support to be removed in -curr, Matt Thomas
  • Re: TP4 over IP and EON support to be removed in -, Antti Kantee
  • Re: TP4 over IP and EON support to be removed in -, Ignatios Souvatzis
    • Re: TP4 over IP and EON support to be removed in -, Nick Hudson
      • Re: TP4 over IP and EON support to be removed in -, Antti Kantee
      • Re: TP4 over IP and EON support to be removed in -, Ignatios Souvatzis
      • Re: TP4 over IP and EON support to be removed in -, Johnny Billquist
      • Re: TP4 over IP and EON support to be removed in -, Robert Elz
• modules in -current, Alexander Shishkin
  • Re: modules in -current, Andy Shevchenko
• Path to kmods, Mindaugas Rasiukevicius
  • Re: Path to kmods, Andrew Doran
    • Re: Path to kmods, Hubert Feyrer
      • Re: Path to kmods, vincent
      • Re: Path to kmods, Michael
      • Re: Path to kmods, Christoph Egger
      • Re: Path to kmods, Quentin Garnier
      • Re: Path to kmods, Christoph Egger
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Robert Elz
      • Re: Path to kmods, Johnny Billquist
      • Re: Path to kmods, Matt Thomas
      • Re: Path to kmods, Johnny Billquist
      • Re: Path to kmods, Hubert Feyrer
      • Re: Path to kmods, Rhialto
      • Re: Path to kmods, Jochen Kunz
      • Re: Path to kmods, der Mouse
      • Re: Path to kmods, der Mouse
      • Re: Path to kmods, Jared D. McNeill
      • Re: Path to kmods, Johnny Billquist
      • re: Path to kmods, matthew green
      • Re: Path to kmods, Robert Elz
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Christoph Egger
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Bill Stouder-Studenmund
      • Re: Path to kmods, Antti Kantee
      • Re: Path to kmods, Hubert Feyrer
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Greg A. Woods; Planix, Inc.
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Greg A. Woods; Planix, Inc.
      • Re: Path to kmods, matthew sporleder
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, matthew sporleder
      • Re: Path to kmods, Herb Peyerl
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Herb Peyerl
      • Re: Path to kmods, Hubert Feyrer
      • Re: Path to kmods, Joerg Sonnenberger
      • Re: Path to kmods, Christoph Egger
      • Re: Path to kmods, Joerg Sonnenberger
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Herb Peyerl
      • Re: Path to kmods, Joerg Sonnenberger
      • Re: Path to kmods, Rhialto
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Adam Hoka
      • Re: Path to kmods, Juergen Hannken-Illjes
      • Re: Path to kmods, Christoph Egger
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Hubert Feyrer
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Manuel Bouyer
      • Re: Path to kmods, Andrew Doran
      • Re: Path to kmods, Antti Kantee
      • Re: Path to kmods, Steven M. Bellovin
      • Re: Path to kmods, Herb Peyerl
      • Re: Path to kmods, Andrew Doran
• Weird revivesa issue, Bill Stouder-Studenmund
• Realtek ALC268 support in azalia_codec, Yorick Hardy
  • Re: Realtek ALC268 support in azalia_codec, Jared D. McNeill
    • Re: Realtek ALC268 support in azalia_codec, Yorick Hardy
      • Re: Realtek ALC268 support in azalia_codec, Jared D. McNeill
  • Re: Realtek ALC268 support in azalia_codec, Andy Shevchenko
• -current panic on amd64, Jukka Marin
  • Re: -current panic on amd64, Martti Kuparinen
    • Re: -current panic on amd64, john heasley
      • Re: -current panic on amd64, john heasley
  • Re: -current panic on amd64, Martti Kuparinen
    • Re: -current panic on amd64, Jukka Marin
      • Re: -current panic on amd64, Matthias Scheler
      • Re: -current panic on amd64, Izumi Tsutsui
      • Re: -current panic on amd64, Jukka Marin
      • Re: -current panic on amd64, Matthias Scheler
      • Re: -current panic on amd64, Izumi Tsutsui
• RFC: NUMA support, Christoph Egger
  • Re: RFC: NUMA support, Manuel Bouyer
    • Re: RFC: NUMA support, Christoph Egger
      • Re: RFC: NUMA support, Manuel Bouyer
  • Re: RFC: NUMA support, Rhialto
• Questions regarding acpi_tz(4), Paul Goyette
  • Re: Questions regarding acpi_tz(4), Joerg Sonnenberger
    • Re: Questions regarding acpi_tz(4), Paul Goyette
      • Re: Questions regarding acpi_tz(4), Joerg Sonnenberger
      • Re: Questions regarding acpi_tz(4), Paul Goyette
• Include spdmem(4) in GENERIC amd64 & i386 kernels?, Paul Goyette
  • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Thor Lancelot Simon
    • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Paul Goyette
  • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Joerg Sonnenberger
    • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Michael
    • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Paul Goyette
      • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Jochen Kunz
      • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Michael
      • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Jochen Kunz
      • Re: Include spdmem(4) in GENERIC amd64 & i386 kern, Michael
• wsdisplay_kbdholdscreen(), Havard Eidnes
  • Re: wsdisplay_kbdholdscreen(), Matthias Drochner
• interrupt storm on int19, Geert Hendrickx
  • Re: interrupt storm on int19, Geert Hendrickx
• locking/synchronization changes 4.99.66->now? (bro, Thor Lancelot Simon
  • Re: locking/synchronization changes 4.99.66->now? , Thor Lancelot Simon
  • Re: locking/synchronization changes 4.99.66->now? , Bill Stouder-Studenmund
• NFS-related crashes, Emmanuel Dreyfus
• Re: kern/39608: bge(4) constant freeze on BCM5906M, Joel Carnat
  • <Possible follow-ups>
  • Re: kern/39608: bge(4) constant freeze on BCM5906M, Karl Uwe Lockhoff
    • Re: kern/39608: bge(4) constant freeze on BCM5906M, Ignatios Souvatzis
      • Re: kern/39608: bge(4) constant freeze on BCM5906M, Christoph Egger
• would a mutex_wait be useful?, Matt Thomas
  • Re: would a mutex_wait be useful?, Adam Hamsik
    • Re: would a mutex_wait be useful?, Matt Thomas
      • Re: would a mutex_wait be useful?, Jean-Yves Migeon
  • Re: would a mutex_wait be useful?, Mindaugas Rasiukevicius
    • Re: would a mutex_wait be useful?, Matt Thomas
      • Re: would a mutex_wait be useful?, Antti Kantee
      • Re: would a mutex_wait be useful?, Mindaugas Rasiukevicius
      • Re: would a mutex_wait be useful?, Mindaugas Rasiukevicius
      • Re: would a mutex_wait be useful?, Christos Zoulas
      • Re: would a mutex_wait be useful?, Antti Kantee
      • Re: would a mutex_wait be useful?, Mindaugas Rasiukevicius
      • Re: would a mutex_wait be useful?, Joerg Sonnenberger
• sys/arch/i386/clock.h: WTF?, Thor Lancelot Simon
  • Re: sys/arch/i386/clock.h: WTF?, Bernd Ernesti
    • Re: sys/arch/i386/clock.h: WTF?, Joerg Sonnenberger
  • Re: sys/arch/i386/clock.h: WTF?, Simon Burge