linux-kernel  

Messages by Thread

• • Re: test10-pre7 Russell King
  • Re: test10-pre7 Linus Torvalds
  • Re: test10-pre7 (LINK ordering) Randy Dunlap
  • Re: test10-pre7 (LINK ordering) Jeff Garzik
  • Re: test10-pre7 Peter Samuelson
  • Re: test10-pre7 Keith Owens
  • Re: test10-pre7 Alan Cox
  • Re: test10-pre7 Peter Samuelson
  • Re: test10-pre7 John Alvord
  • Re: test10-pre7 Peter Samuelson
  • Re: test10-pre7 Rogier Wolff
  • Re: test10-pre7 Michael Elizabeth Chastain
  • Re: test10-pre7 Christoph Hellwig
  • Re: test10-pre7 Vladislav Malyshkin
  • Re: test10-pre7 Peter Samuelson
  • Re: test10-pre7 Vladislav Malyshkin
  • Re: test10-pre7 Linus Torvalds
  • Re: test10-pre7 H. Peter Anvin
  • Re: test10-pre7 Peter Samuelson
  • Re: test10-pre7 H. Peter Anvin
  • Linus's poll variation Lyle Coder
  • Re: test10-pre7 Peter Samuelson
  • Re: test10-pre7 Peter Samuelson
  • Re: test10-pre7 Vladislav Malyshkin
• Third arg to switch_to() Kenn Humborg
  • Re: Third arg to switch_to() Kenn Humborg
• hard_sector / hard_nr_sectors Al Peat
  • Re: hard_sector / hard_nr_sectors Andrea Arcangeli
• installing an ISR from user code Brett Smith
  • Re: installing an ISR from user code rread
  • Re: installing an ISR from user code Tim Waugh
  • Re: installing an ISR from user code Richard B. Johnson
  • Re: installing an ISR from user code Anton Altaparmakov
• 2.2.18pre15 oops in find_buffer() Mikael Pettersson
  • Re: 2.2.18pre15 oops in find_buffer() adrian
• kmalloc() allocation. Richard B. Johnson
  • Re: kmalloc() allocation. Tigran Aivazian
  • Re: kmalloc() allocation. Richard B. Johnson
  • Re: kmalloc() allocation. Tigran Aivazian
  • Re: kmalloc() allocation. Richard B. Johnson
  • Re: kmalloc() allocation. John Levon
  • Re: kmalloc() allocation. Richard B. Johnson
  • Re: kmalloc() allocation. Jeff Garzik
  • Re: kmalloc() allocation. Tigran Aivazian
  • Re: kmalloc() allocation. Jeff Garzik
  • Re: kmalloc() allocation. Richard B. Johnson
  • Re: kmalloc() allocation. Richard B. Johnson
  • Re: kmalloc() allocation. Jeff Garzik
  • Re: kmalloc() allocation. Rik van Riel
  • Re: kmalloc() allocation. Mike Galbraith
  • Re: kmalloc() allocation. Ingo Oeser
  • Re: kmalloc() allocation. Rik van Riel
  • Re: kmalloc() allocation. Richard B. Johnson
  • Re: kmalloc() allocation. Pauline Middelink
  • Re: kmalloc() allocation. Ingo Oeser
  • Re: kmalloc() allocation. Rik van Riel
  • Re: kmalloc() allocation. Ingo Oeser
  • Re: kmalloc() allocation. afei
  • Re: kmalloc() allocation. Alan Cox
  • Re: kmalloc() allocation. Richard B. Johnson
  • Re: kmalloc() allocation. H. Peter Anvin
  • Re: kmalloc() allocation. Brian Gerst
  • Re: kmalloc() allocation. Andi Kleen
  • Re: kmalloc() allocation. Brian Gerst
  • Re: kmalloc() allocation. kernel
  • Re: kmalloc() allocation. Alan Cox
  • Re: kmalloc() allocation. kernel
  • Re: kmalloc() allocation. Tigran Aivazian
  • Re: kmalloc() allocation. Andi Kleen
  • Re: kmalloc() allocation. Tigran Aivazian
  • Re: kmalloc() allocation. Andi Kleen
  • Re: kmalloc() allocation. Mark W. McClelland
• Support for Compaq's NC3134 & NC3135 via the eepro100.o (82559 chip)? J{rvensivu Riku
  • Re: Support for Compaq's NC3134 & NC3135 via the eepro100.o (82559chip) ? Tigran Aivazian
• [PATCH] update to SysRQ registration patch Crutcher Dunnavant
• Locking Between User Context and Soft IRQs in 2.4.0 Hen, Shmulik
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Jeff Garzik
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Andi Kleen
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Jeff Garzik
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Andi Kleen
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Jeff Garzik
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Andi Kleen
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Andrew Morton
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Andrew Morton
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Andi Kleen
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Keith Owens
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Keith Owens
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Andrew Morton
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Paul Gortmaker
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Andrew Morton
  • Re: Locking Between User Context and Soft IRQs in 2.4.0 Rusty Russell
• [PATCH] TracerPid in /proc/<n>/status is wrong Mike Coleman
• dropping untracked packets patch for 2.4 (fwd) Thomas Molina
• Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Linux Kernel Developer
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 J . A . Magallon
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Keith Owens
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Linux Kernel Developer
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Alan Cox
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Keith Owens
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Alan Cox
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Keith Owens
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Alan Cox
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Keith Owens
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Alan Cox
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Keith Owens
  • Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Linux Kernel Developer
• FIFO-Scheduling in Kernel 2.2 Christoph Pleger
• [ANNOUNCE] SUBTERFUGUE 0.1.99 mkc
  • [ANNOUNCE] SUBTERFUGUE 0.1.99a (bugfix) Mike Coleman
• bug or what?? Marco Zanon
• Questions on lack of piix4 usb interrupts Adam J. Richter
  • Re: Questions on lack of piix4 usb interrupts Maciej W. Rozycki
• Patch: modularizing partition parsing in linux-2.4.0-test10-pre6 Adam J. Richter
• initrd broken??? Jeff Chua
• / on ramfs, possible? Anders Eriksson
  • Re: / on ramfs, possible? H. Peter Anvin
  • Re: / on ramfs, possible? David Woodhouse
  • Re: / on ramfs, possible? H. Peter Anvin
  • Re: / on ramfs, possible? David Woodhouse
  • Re: / on ramfs, possible? H. Peter Anvin
  • Re: / on ramfs, possible? Jeff Garzik
  • Re: / on ramfs, possible? aer-list
  • Re: / on ramfs, possible? Alan Cox
  • Re: / on ramfs, possible? Stuart Lynne
  • Re: / on ramfs, possible? Adam J. Richter
  • cool dev help.. Akbar A.
• Re: tcp.c::wait_for_tcp_memory() buggy ? Ingo Molnar
• Re: [PATCH] Re: Negative scalability by removal of lock_kernel()?(Was: Andi Kleen
  • Re: [PATCH] Re: Negative scalability by removal of lock_kernel()?(Was: Andrea Arcangeli
• /proc & xml data Joe
  • Re: /proc & xml data Eric W. Biederman
  • Re: /proc & xml data Moritz Schulte
  • Re: /proc & xml data Olaf Titz
  • Re: Re: /proc & xml data joeja
• bug fix for 'include/linux/wrapper.h', bad parentheses for macros Kevin Lawton
  • PATCH 2.4.0.10.6: wrapper.h cleanup Jeff Garzik
• kernel 2.4.0-test9 nd bttv vwbug
  • Re: kernel 2.4.0-test9 nd bttv Erik Mouw
• POSIX message queue support in Linux kernel? Craig Rodrigues
• Readiness vs. completion (was: Re: Linux's implementation of poll()not scalable?) Dan Kegel
  • Re: Readiness vs. completion (was: Re: Linux's implementation ofpoll()not scalable?) John Gardiner Myers
  • Re: Readiness vs. completion (was: Re: Linux's implementationofpoll()not scalable?) Dan Kegel
  • Re: Readiness vs. completion (was: Re: Linux'simplementationofpoll()not scalable?) John Gardiner Myers
• 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Andi Kleen
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Andi Kleen
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Andrea Arcangeli
  • Re: 2.2.18Pre Lan Performance Rocks! Chris Evans
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Andrea Arcangeli
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Dan Hollis
  • Re: 2.2.18Pre Lan Performance Rocks! Pavel Machek
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! john slee
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Alan Cox
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Alan Cox
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Erik Andersen
  • Re: 2.2.18Pre Lan Performance Rocks! Pavel Machek
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
  • Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
  • Re: 2.2.18Pre Lan Performance Rocks! Davide Libenzi
  • Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey

[Earlier messages] [Later messages]