Mail Index

• Thread Index

• jiffies
  • From: ninjaboy
• Re: jiffies
  • From: Min-Hua Chen
• Re: jiffies
  • From: ninjaboy
• Re: serial port driver with ppp hangs
  • From: endeavor john
• Re: Doubt regarding memory
  • From: Mulyadi Santosa
• Re: jiffies
  • From: Rajat Jain
• Re: netfilter hook questions
  • From: Mulyadi Santosa
• sock_sendmsg from interrupt context
  • From: endeavor john
• Re: sock_sendmsg from interrupt context
  • From: kanishk rastogi
• Re: netfilter hook questions
  • From: topi
• Re: jiffies
  • From: Min-Hua Chen
• Re: Doubt regarding memory
  • From: Tzahi Fadida
• help with dev_queue_xmit
  • From: Cristian Zamfir
• network loopback based kernle module and ping - calrification question
  • From: Mark Ryden
• some simple questions about sysfs
  • From: Robert P. J. Day
• Saving/Restoring 64 bits width data into two 32 bits
  • From: Ye ilho
• Re: Supply Of Materials
  • From: Niger Delta Development Commission
• read from /proc stalls
  • From: Greg Martyn
• learning the kernel
  • From: Lazlo Hollyfield
• Problem with LOCAL_IN hook
  • From: Kanhu Rauta
• Re: learning the kernel
  • From: Mulyadi Santosa
• Re: some simple questions about sysfs
  • From: Greg KH
• Re: Re: Doubt regarding memory
  • From: Mulyadi Santosa
• Re: network loopback based kernle module and ping - calrification question
  • From: Mulyadi Santosa
• Re: Saving/Restoring 64 bits width data into two 32 bits
  • From: Andrea Gasparini
• Policy Violation
  • From: Symantec_Mail_Security_for_SMTP
• Re: learning the kernel
  • From: Robert P. J. Day
• Re: learning the kernel
  • From: Milind Choudhary
• Re: Doubt regarding memory
  • From: Tzahi Fadida
• Re: Doubt regarding memory
  • From: Erik Mouw
• Re: some simple questions about sysfs
  • From: Robert P. J. Day
• Re: Doubt regarding memory
  • From: Daniel Weidele
• Re: Doubt regarding memory
  • From: Erik Mouw
• Unsubscribe..
  • From: Ravi Shankar
• Re: Unsubscribe..
  • From: Erik Mouw
• Re: some simple questions about sysfs
  • From: Greg KH
• Re: some simple questions about sysfs
  • From: Robert P. J. Day
• Re: some simple questions about sysfs
  • From: Greg KH
• Re: network loopback based kernle module and ping - calrification question
  • From: Mark Ryden
• question about PG_highmem flag
  • From: kashif saeed
• Re: question about PG_highmem flag
  • From: Fawad Lateef
• write_seqlock in timer
  • From: ninjaboy
• cghlhhihqpnmtm
  • From: vik
• A pleasant surprise...
  • From: A.R.Karthick
• Re: Doubt regarding memory
  • From: Mulyadi Santosa
• Re: Unsubscribe..
  • From: Erik Mouw
• just how important are POSIX message queues?
  • From: Robert P. J. Day
• Re: just how important are POSIX message queues?
  • From: Mattia Dongili
• Re: just how important are POSIX message queues?
  • From: Robert P. J. Day
• Re: Re: network loopback based kernle module and ping - calrification question
  • From: Mulyadi Santosa
• Linking error
  • From: Rafał Bilski
• Re: Linking error
  • From: Nish Aravamudan
• Re: Linking error
  • From: Rafał Bilski
• Re: Linking error
  • From: Adrian Bunk
• Re: Linking error
  • From: Rafał Bilski
• Re: Doubt regarding memory
  • From: Tzahi Fadida
• Re: network loopback based kernle module and ping - calrification question
  • From: Rajat Jain
• Sunil has Tagged you! :)
  • From: Sunil Agham
• Sunil has Tagged you! :)
  • From: Sunil Agham
• Multiprocessing
  • From: David B. Held
• =?iso-8859-2?Q?many_sockets_slow_down_sendto??=
  • From: Zaccomer Lajos
• Re: Sunil has Tagged you! :)
  • From: सुिनल अघम ( Sunil Agham )
• How to find the list and number of processes opened by a process?
  • From: Prasad Joshi
• Re: How to find the list and number of processes opened by a process?
  • From: Erik Mouw
• Re: How to find the list and number of processes opened by a process?
  • From: Prasad Joshi
• Re: How to find the list and number of processes opened by a process?
  • From: Erik Mouw
• Re: How to find the list and number of processes opened by a process?
  • From: Martin Mancuska
• Welcome to Tagged!
  • From: Tagged
• Re: How to find the list and number of processes opened by a process?
  • From: Avishay Traeger
• Re: How to find the list and number of files opened by a process?
  • From: Prasad Joshi
• Su mensaje no ha sido entregado por violar la politica "ExtentionFilter"
  • From: InterScan MSS Notification
• Re: learning the kernel
  • From: Dequan Yang
• About Kernel Backtrace
  • From: railroad seeker
• Re: About Kernel Backtrace
  • From: Rajat Jain
• How to find free port
  • From: Rajath N R
• Re: How to find free port
  • From: Kaushal Shriyan
• Re: network loopback based kernle module and ping - calrification question
  • From: kashif saeed
• Cleaning up unrequired #include(s)
  • From: Rajat Jain
• Re: How to find the list and number of processes opened by a process?
  • From: Prasad Joshi
• Makefile for module with multiple directories
  • From: Rick Brown
• Re: Makefile for module with multiple directories
  • From: Prasad Joshi
• Problem with local in hook
  • From: Kanhu Rauta
• smp/non-smp kernel
  • From: my linux
• Re: smp/non-smp kernel
  • From: Rajat Jain
• Re: smp/non-smp kernel
  • From: my linux
• Received Warnings and errors while compiling the Fedora Linux kernel
  • From: Irfan Ahmed
• Re: smp/non-smp kernel
  • From: Prasad Joshi
• Re: smp/non-smp kernel
  • From: my linux
• Re: Received Warnings and errors while compiling the Fedora Linux kernel
  • From: Prasad Joshi
• Re: netfilter hook questions
  • From: Hayim Shaul
• Re: smp/non-smp kernel
  • From: Prasad Joshi
• Returned mail: Data format error
  • From: bpaulson
• Re: Received Warnings and errors while compiling the Fedora Linux kernel
  • From: Martin Mancuska
• Re: Received Warnings and errors while compiling the Fedora Linux kernel
  • From: Prasad Joshi
• Re: Received Warnings and errors while compiling the Fedora Linux kernel
  • From: Erik Mouw
• asmlinkage and C++ query!!!
  • From: Pradeep Singh, TLS-Chennai
• TSS and linux kernel
  • From: Pradeep Singh, TLS-Chennai
• Re: asmlinkage and C++ query!!!
  • From: Erik Mouw
• what are pre-patches?
  • From: Himanshu Chauhan
• Re: what are pre-patches?
  • From: Martin Mancuska
• Re: what are pre-patches?
  • From: Himanshu Chauhan
• Re: what are pre-patches?
  • From: Randy Dunlap
• Re: smp/non-smp kernel
  • From: Rajat Jain
• Debugging kernel with KGDB
  • From: Daniel Rodrick
• Re: How to find free port
  • From: Roman Mashak
• Re: smp/non-smp kernel
  • From: Rajat Jain
• compile 2.4.x kernel on 2.6.x distribution
  • From: kashif saeed
• Re: smp/non-smp kernel
  • From: my linux
• Re: About Kernel Backtrace
  • From: railroad seeker
• Re: compile 2.4.x kernel on 2.6.x distribution
  • From: Erik Mouw
• Re: TSS and linux kernel
  • From: Ahmed S. Darwish
• RE: TSS and linux kernel
  • From: Pradeep Singh, TLS-Chennai
• Thread safe circular buffer.
  • From: Tzahi Fadida
• udev: isn't 'NAME="%k"' redundant?
  • From: Robert P. J. Day
• Re: Thread safe circular buffer.
  • From: Tzahi Fadida
• Re: Thread safe circular buffer.
  • From: Stuart Macdonald
• Re: Thread safe circular buffer.
  • From: Tzahi Fadida
• Re: Thread safe circular buffer.
  • From: burns . ethan
• [PATCH 2.6.21-rc3] i386: Fix GDT's number of quadwords in comment
  • From: Ahmed S. Darwish
• Re: [PATCH 2.6.21-rc3] i386: Fix GDT's number of quadwords in comment
  • From: Ahmed S. Darwish
• IP Defragmentation
  • From: Kanhu Rauta
• locking file on smp based kernel with multi-threadng
  • From: Deepak Joshi
• Re: Thread safe circular buffer.
  • From: Stavros Passas
• Re: Thread safe circular buffer.
  • From: Anupam Kapoor
• Re: Thread safe circular buffer.
  • From: Tzahi Fadida
• Re: locking file on smp based kernel with multi-threadng
  • From: Jesper Juhl
• distribution kits
  • From: Roman Mashak
• Re: distribution kits
  • From: Jesper Juhl
• Re: Thread safe circular buffer.
  • From: Stuart Macdonald
• Re: smp/non-smp kernel
  • From: Arjan van de Ven
• 2.4 kernel parameters of a N2200
  • From: Christian Schaefer
• Re: Thread safe circular buffer.
  • From: Greg Freemyer
• How to print out socket related data in the kernel?
  • From: Ye ilho
• Re: How to print out socket related data in the kernel?
  • From: Ye ilho
• Re: How to print out socket related data in the kernel?
  • From: Tetsuo Handa
• Re: distribution kits
  • From: Roman Mashak
• How to deliberately dump a kernel stack?
  • From: railroad seeker
• Re: smp/non-smp kernel
  • From: my linux
• more than 65535 outbound connections
  • From: Niklaus
• Re: Thread safe circular buffer.
  • From: Momchil Velikov
• Re: 2.4 kernel parameters of a N2200
  • From: Erik Mouw
• Fwd: more than 65535 outbound connections
  • From: Niklaus
• cpu info 64bit/32bit
  • From: Deepak Joshi
• Re: cpu info 64bit/32bit
  • From: Martin Mancuska
• Re: cpu info 64bit/32bit
  • From: Erik Mouw
• Re: cpu info 64bit/32bit
  • From: Sandeep Kumar
• Re: cpu info 64bit/32bit
  • From: Tzahi Fadida
• Re: smp/non-smp kernel
  • From: Arjan van de Ven
• Re: more than 65535 outbound connections
  • From: Greg Freemyer
• magic sysrq question
  • From: Ye ilho
• Re: magic sysrq question
  • From: Mike Frysinger
• Re: magic sysrq question
  • From: Randy Dunlap
• hpet_test doesn't work
  • From: ninjaboy
• Re: more than 65535 outbound connections
  • From: Bernd Petrovitsch
• Re: magic sysrq question
  • From: Mike Frysinger
• Re: magic sysrq question
  • From: Randy Dunlap
• how does the architecture affect browsing code at lxr.linux.no?
  • From: Robert P. J. Day
• ping DOS avoidance?
  • From: Luis Carlos Cobo Rus
• I2C dilemma and lm_sensors
  • From: Ramagudi Naziir
• Problem with registering security structure.
  • From: Prasad Joshi
• dynamic allocation of devices and udev
  • From: Himanshu Chauhan
• I2C and interrupts
  • From: Ramagudi Naziir
• Re: dynamic allocation of devices and udev
  • From: Greg KH
• glossary for gcc attributes used by kernel?
  • From: Robert P. J. Day
• Re: IP Defragmentation
  • From: Jan Engelhardt
• Re: glossary for gcc attributes used by kernel?
  • From: Rajat Jain
• GPIO interrupt on PC ?
  • From: Ramagudi Naziir
• "u area" virtual address
  • From: Abhijit Pawar
• notifiers to user space
  • From: Ramagudi Naziir
• Re: notifiers to user space
  • From: Ramagudi Naziir
• Re: notifiers to user space
  • From: Tzahi Fadida
• Re: notifiers to user space
  • From: Asim
• Re: notifiers to user space
  • From: Ramagudi Naziir
• Re: glossary for gcc attributes used by kernel?
  • From: Mike Frysinger
• Re: notifiers to user space
  • From: Himanshu Chauhan
• kmem_getpages() and High Memory
  • From: Dong Feng
• Re: notifiers to user space
  • From: Rajat Jain
• Block Async I/O
  • From: Nirmal Thacker
• RE: "u area" virtual address
  • From: Ajay Singh \(ajaysi\)
• Re: "u area" virtual address
  • From: Abhijit Pawar
• Re: notifiers to user space
  • From: Ramagudi Naziir
• Re: notifiers to user space
  • From: Ramagudi Naziir
• Re: Block Async I/O
  • From: Randy.Dunlap
• Re: notifiers to user space
  • From: Rajat Jain
• RE: "u area" virtual address
  • From: Ajay Singh \(ajaysi\)
• Re: notifiers to user space
  • From: Asim
• Writing inode_operations->create() function.
  • From: Prasad Joshi
• Re: glossary for gcc attributes used by kernel?
  • From: Robert P. J. Day
• Problem with IP defragmentation in 2.6 kernel
  • From: Kanhu Rauta
• Re: Writing inode_operations->create() function.
  • From: Prasad Joshi
• Re: Writing inode_operations->create() function.
  • From: Avishay Traeger
• Re: Writing inode_operations->create() function.
  • From: Prasad Joshi
• Re: GPIO interrupt on PC ?
  • From: Erik Mouw
• Re: smp/non-smp kernel
  • From: my linux
• Re: Writing inode_operations->create() function.
  • From: Avishay Traeger
• Re: Writing inode_operations->create() function.
  • From: Prasad Joshi
• Re: Writing inode_operations->create() function.
  • From: Prasad Joshi
• Re: Writing inode_operations->create() function.
  • From: Avishay Traeger
• Re: Writing inode_operations->create() function.
  • From: Prasad Joshi
• How to find the pid of the a given process.
  • From: Prasad Joshi
• Different debugging styles (was: glossary for gcc attributes used by kernel?)
  • From: Mike Frysinger
• Re: Different debugging styles (was: glossary for gcc attributes used by kernel?)
  • From: Robert P. J. Day
• Re: How to find the pid of the a given process.
  • From: Erik Mouw
• Re: How to find the pid of the a given process.
  • From: santosh dwivedi
• Re: How to find the pid of the a given process.
  • From: Avishay Traeger
• ERR_PTR and PTR_ERR
  • From: Ming Zhang
• Re: How to find the pid of the a given process.
  • From: Erik Mouw
• Re: smp/non-smp kernel
  • From: Arjan van de Ven
• Re: How to find the pid of the a given process.
  • From: Prasad Joshi
• Re: How to find the pid of the a given process.
  • From: Amol Lad
• Re: How to find the pid of the a given process.
  • From: Erik Mouw
• Hey, you have a new Greeting !!!
  • From: Greetings.com
• Hey, you have a new Greeting !!!
  • From: Greetings.com
• query related to APIC and kernel
  • From: Pradeep Singh, TLS-Chennai
• Re: query related to APIC and kernel
  • From: Erik Mouw
• =?tis-620?b?xbS56dPLudGhIKKo0bTkosHRuSDB0ei54w==?==?tis-620?b?qOTD6crox7ngodS5ILTpx8LH1LjVp+jSwuY=?=
  • From: suphat madsung
• class_device_create_file warnings during compilation
  • From: Dinesh
• Re: class_device_create_file warnings during compilation
  • From: Nish Aravamudan
• Re: class_device_create_file warnings during compilation
  • From: Mike Frysinger
• CIFS too slow on x86_64 machine.
  • From: penguin-newbie
• Re: class_device_create_file warnings during compilation
  • From: Prasad Joshi
• Re: class_device_create_file warnings during compilation
  • From: Prasad Joshi
• Re: class_device_create_file warnings during compilation
  • From: Prasad Joshi
• How does boot loader tell the kernel, the location of initrd?
  • From: Rajat Jain
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: Shakthi Kannan
• ip_rt_ioctl woes
  • From: lee nookx
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: Rajendra
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: Rajat Jain
• Online Banking Urgent Security Notice
  • From: Halifax Bank PLC
• system call for setfacl
  • From: Deepak Joshi
• RE: system call for setfacl
  • From: Ajay Singh \(ajaysi\)
• Is UML patches available for 2.6.20 kernel?
  • From: Prasad Joshi
• i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: Ahmed S. Darwish
• Re: system call for setfacl
  • From: Greg Freemyer
• Re: Is UML patches available for 2.6.20 kernel?
  • From: Prasad Joshi
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: Thierry Reding
• How to identify a thread from task_struct
  • From: Irfan Habib
• irq routine and i2c_transfer
  • From: borasahin
• Re: How to identify a thread from task_struct
  • From: Mulyadi Santosa
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: Mulyadi Santosa
• Re: How to identify a thread from task_struct
  • From: Sandeep Sanjay Patil
• doubt regarding kmalloc() in fs/super.c
  • From: anand muttagi
• Re: How to identify a thread from task_struct
  • From: Ahmed S. Darwish
• Re: ERR_PTR and PTR_ERR
  • From: Randy Dunlap
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: Rajat Jain
• How to let INITRAMFS continue as root filesystem?
  • From: Rajat Jain
• Re: How to let INITRAMFS continue as root filesystem?
  • From: Rajat Jain
• Re: irq routine and i2c_transfer
  • From: Erik Mouw
• Re: ERR_PTR and PTR_ERR
  • From: Ming Zhang
• Re: ERR_PTR and PTR_ERR
  • From: Avishay Traeger
• Re: ERR_PTR and PTR_ERR
  • From: Ming Zhang
• Re: ERR_PTR and PTR_ERR
  • From: Randy Dunlap
• Re: ERR_PTR and PTR_ERR
  • From: Ming Zhang
• Re: ERR_PTR and PTR_ERR
  • From: Avishay Traeger
• Re: ERR_PTR and PTR_ERR
  • From: Ming Zhang
• How to keep track of socket close()?
  • From: Ye ilho
• Understanding PCI
  • From: Tzahi Fadida
• Re: glossary for gcc attributes used by kernel?
  • From: Przemek Lib
• recursive locking in linux?
  • From: Robert P. J. Day
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: Ahmed S. Darwish
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: Mulyadi Santosa
• Re: How to keep track of socket close()?
  • From: Ye ilho
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: Ahmed S. Darwish
• Direct VFS/SB Access and Private Submounting
  • From: John Anthony Kazos Jr.
• Re: recursive locking in linux?
  • From: Arjan van de Ven
• Compiling 2.6.20-mm2 for Sparc64
  • From: Alexander Surma
• how much of the kernel address space is used for virtual addresses?
  • From: Robert P. J. Day
• Emitting an ignore_int() handled interrupt and system response
  • From: Ahmed S. Darwish
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: Ahmed S. Darwish
• kernel crash dump anomaly (scheduling in interrupt)
  • From: railroad seeker
• Re: recursive locking in linux?
  • From: Daniel Rodrick
• Re: how much of the kernel address space is used for virtual addresses?
  • From: Daniel Rodrick
• Re: Emitting an ignore_int() handled interrupt and system response
  • From: Rajat Jain
• Re: recursive locking in linux?
  • From: Arjan van de Ven
• Re: how much of the kernel address space is used for virtual addresses?
  • From: Robert P. J. Day
• Re: how much of the kernel address space is used for virtual addresses?
  • From: Rajat Jain
• Received a panic while closing the file.
  • From: Prasad Joshi
• Re: recursive locking in linux?
  • From: Robert P. J. Day
• Re: recursive locking in linux?
  • From: Momchil Velikov
• Re: recursive locking in linux?
  • From: Momchil Velikov
• Re: recursive locking in linux?
  • From: Arjan van de Ven
• Re: recursive locking in linux?
  • From: Robert P. J. Day
• Re: recursive locking in linux?
  • From: Robert P. J. Day
• Re: Understanding PCI
  • From: Erik Mouw
• Re: recursive locking in linux?
  • From: Daniel Rodrick
• Re: recursive locking in linux?
  • From: Daniel Rodrick
• help me to understand __atomic_hash()
  • From: N Cocy
• Re: recursive locking in linux?
  • From: matze
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: pradeep singh
• Re: recursive locking in linux?
  • From: Robert P. J. Day
• Re: recursive locking in linux?
  • From: Robert P. J. Day
• Re: recursive locking in linux?
  • From: matze
• Allocated kernel memory not page aligned??...
  • From: Kris van Rens
• Re: recursive locking in linux?
  • From: matze
• Re: Emitting an ignore_int() handled interrupt and system response
  • From: Ahmed S. Darwish
• Re: recursive locking in linux?
  • From: Arjan van de Ven
• Re: Compiling 2.6.20-mm2 for Sparc64
  • From: Randy Dunlap
• Re: help me to understand __atomic_hash()
  • From: topi
• Re: help me to understand __atomic_hash()
  • From: Robert P. J. Day
• Re: Emitting an ignore_int() handled interrupt and system response
  • From: Daniel Cheng
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: Ahmed S. Darwish
• Re: recursive locking in linux?
  • From: Arjan van de Ven
• ACL --- chmod and setfacl
  • From: Deepak Joshi
• Re: ACL --- chmod and setfacl
  • From: Avishay Traeger
• Re: Emitting an ignore_int() handled interrupt and system response
  • From: Ahmed S. Darwish
• Re: ACL --- chmod and setfacl
  • From: Rajat Jain
• kernel start addr
  • From: ninjaboy
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: pradeep singh
• doubt about VMA struct
  • From: pradeep singh
• Re: doubt about VMA struct
  • From: sandeep lahane
• Re: kernel crash dump anomaly (scheduling in interrupt)
  • From: sandeep lahane
• Re: recursive locking in linux?
  • From: Daniel Rodrick
• Re: recursive locking in linux?
  • From: Arjan van de Ven
• Re: Doubt regarding memory
  • From: Mansha Linux
• Re: doubt about VMA struct
  • From: pradeep singh
• Re: doubt about VMA struct
  • From: Ahmed S. Darwish
• query related to different architectures
  • From: Rick Brown
• Re: query related to different architectures
  • From: Mike Frysinger
• Re: kernel start addr
  • From: Thomas Petazzoni
• Re: kernel start addr
  • From: ninjaboy
• Need for a new spinlock API?
  • From: Rajat Jain
• Re: doubt about VMA struct
  • From: pradeep singh
• need for mmap?
  • From: Daniel Rodrick
• need for 3G/1G split
  • From: Rick Brown
• kernel preemption
  • From: Rick Brown
• Re: doubt about VMA struct
  • From: Rajat Jain
• Re: kernel preemption
  • From: Mansha Linux
• Re: doubt about VMA struct
  • From: sandeep lahane
• Really newbie ;-)
  • From: Latchezar Kostov
• directio for device memory
  • From: Ameya Mitragotri
• Re: need for mmap?
  • From: Arjan van de Ven
• Re: Need for a new spinlock API?
  • From: Arjan van de Ven
• decoding oops.
  • From: Prasad Joshi
• Re: doubt about VMA struct
  • From: pradeep singh
• kernel source link
  • From: Manoj Awasthi
• Re: kernel source link
  • From: Jesper Juhl
• Re: kernel source link
  • From: Neependra Khare
• Re: need for 3G/1G split
  • From: Vivek
• Best solution to experiment with kernel
  • From: Fernando Apesteguía
• Re: Best solution to experiment with kernel
  • From: matze
• Re: Best solution to experiment with kernel
  • From: Randy Dunlap
• Re: Best solution to experiment with kernel
  • From: Nelson Castillo
• Re: Best solution to experiment with kernel
  • From: Avishay Traeger
• Re: Really newbie ;-)
  • From: Erik Mouw
• contact him immediately,
  • From: desmond chioma
• Re: kernel source link
  • From: Ahmed S. Darwish
• RS232 pin controlling
  • From: Felipe Balbi
• Re: Need for a new spinlock API?
  • From: Arjan van de Ven
• Re: Need for a new spinlock API?
  • From: Tzahi Fadida
• Re: Need for a new spinlock API?
  • From: Rajat Jain
• RE: Need for a new spinlock API?
  • From: Ajay Singh \(ajaysi\)
• Re: Need for a new spinlock API?
  • From: Rajat Jain
• Re: kernel start addr
  • From: Ahmed S. Darwish
• RE: Need for a new spinlock API?
  • From: Ajay Singh \(ajaysi\)
• Re: need for 3G/1G split
  • From: Sandeep Kumar
• Re: need for 3G/1G split
  • From: Prasad Joshi
• Re: Need for a new spinlock API?
  • From: Rajat Jain
• Re: need for 3G/1G split
  • From: Rajat Jain
• Re: Need for a new spinlock API?
  • From: Arjan van de Ven
• Re: Need for a new spinlock API?
  • From: Arjan van de Ven
• Help with understanding PCI
  • From: Tzahi Fadida
• design with spin_locks
  • From: anubhav rakshit
• Re: Help with understanding PCI
  • From: Erik Mouw
• Re: Help with understanding PCI
  • From: Tzahi Fadida
• RE: design with spin_locks
  • From: Ajay Singh \(ajaysi\)
• Re: Help with understanding PCI
  • From: Erik Mouw
• __devinit, __meminit, __cpuinit, etc.
  • From: Robert P. J. Day
• Re: __devinit, __meminit, __cpuinit, etc.
  • From: Randy Dunlap
• Re: Help with understanding PCI
  • From: Tzahi Fadida
• Re: Help with understanding PCI
  • From: Greg KH
• any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Robert P. J. Day
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Mike Frysinger
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Robert P. J. Day
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Greg KH
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Robert P. J. Day
• Re: Help with understanding PCI
  • From: Tzahi Fadida
• Re: Help with understanding PCI
  • From: Shawn Bohrer
• cpu and memory usage
  • From: Deepak Joshi
• Re: cpu and memory usage
  • From: Neependra Khare
• RE: Help with understanding PCI
  • From: krishna.vamsi
• OS Clock
  • From: Bithika Khargharia
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Greg KH
• Re: cpu and memory usage
  • From: mayank rana
• eth_type_trans and protocol field query
  • From: pradeep singh
• RE: Help with understanding PCI
  • From: Martyn Welch
• RE: OS Clock
  • From: Martyn Welch
• RE: RS232 pin controlling
  • From: Martyn Welch
• Re: Help with understanding PCI
  • From: Tzahi Fadida
• Re: Help with understanding PCI
  • From: Tzahi Fadida
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Robert P. J. Day
• Help with writing device driver for RS-485 transceiver
  • From: WANG Zhen
• Re: OS Clock
  • From: Erik Mouw
• Re: Help with writing device driver for RS-485 transceiver
  • From: Erik Mouw
• Re: Help with writing device driver for RS-485 transceiver
  • From: Christian Boon
• core file generation
  • From: Ming Chen
• Re: Help with writing device driver for RS-485 transceiver
  • From: WANG Zhen
• Re: Help with writing device driver for RS-485 transceiver
  • From: WANG Zhen
• confusing passage in Doc.../mutex-design.txt
  • From: Robert P. J. Day
• Re: confusing passage in Doc.../mutex-design.txt
  • From: matze
• Re: confusing passage in Doc.../mutex-design.txt
  • From: Robert P. J. Day
• module registers
  • From: ninjaboy
• Re: module registers
  • From: Mulyadi Santosa
• Re: module registers
  • From: Venkatesh Srinivas
• Re: core file generation
  • From: Mulyadi Santosa
• Re: module registers
  • From: ninjaboy
• Re: OS Clock
  • From: Bithika Khargharia
• Re: need for 3G/1G split
  • From: Mulyadi Santosa
• Re: Best solution to experiment with kernel
  • From: Mulyadi Santosa
• killing NPTL threads
  • From: Ramagudi Naziir
• Sector sizes in the kernel
  • From: Tzahi Fadida
• Re: Best solution to experiment with kernel
  • From: Tzahi Fadida
• You have a new PostCard from a friend
  • From: postcards . com
• You have a new PostCard from a friend
  • From: postcards . com
• Zero Initialized in BSS
  • From: John Anthony Kazos Jr.
• Re: Zero Initialized in BSS
  • From: Neo Jia
• Re: Zero Initialized in BSS
  • From: John Anthony Kazos Jr.
• to get IP address of network interfaces from Kernel space.
  • From: Bizhan Gholikhamseh \(bgholikh\)
• Re: to get IP address of network interfaces from Kernel space.
  • From: Cristian Tapus
• Re: Zero Initialized in BSS
  • From: Daniel Cheng
• identifying kernel version from code files
  • From: Nirmal Thacker
• Re: identifying kernel version from code files
  • From: Prasad Joshi
• Re: Zero Initialized in BSS
  • From: John Anthony Kazos Jr.
• what's the rationale behind kbuild "depends on m"?
  • From: Robert P. J. Day
• You have a new PostCard from a friend
  • From: postcards . com
• can a malloc be *both* GFP_KERNEL and GFP_ATOMIC?
  • From: Robert P. J. Day
• Re: what's the rationale behind kbuild "depends on m"?
  • From: Randy Dunlap
• Re: what's the rationale behind kbuild "depends on m"?
  • From: Robert P. J. Day
• Re: RS232 pin controlling
  • From: Christoph Fritz
• meaning of kernel error messages
  • From: Bernd Schubert
• Re: meaning of kernel error messages
  • From: Rajat Jain
• RE: OS Clock
  • From: Martyn Welch
• RE: Zero Initialized in BSS
  • From: Martyn Welch
• Re: can a malloc be *both* GFP_KERNEL and GFP_ATOMIC?
  • From: Robert P. J. Day
• Re: meaning of kernel error messages
  • From: Bernd Schubert
• RE: Zero Initialized in BSS
  • From: John Anthony Kazos Jr.
• Re: Sector sizes in the kernel
  • From: Erik Mouw
• Re: Help with writing device driver for RS-485 transceiver
  • From: Erik Mouw
• How to get the network details through programming
  • From: Santosh Pradhan
• Optimal Block Size / Max Device Size
  • From: John Anthony Kazos Jr.
• Re: kernel source link
  • From: Manoj Awasthi
• ETXTBSY error
  • From: Manoj Awasthi
• Re: Sector sizes in the kernel
  • From: Tzahi Fadida
• Latency of indirect block mapping in EXT3?
  • From: Seongsu Lee
• Re: Sector sizes in the kernel
  • From: Erik Mouw
• Re: ETXTBSY error
  • From: Daniel Cheng
• Re: Sector sizes in the kernel
  • From: burns . ethan
• Re: Sector sizes in the kernel
  • From: Tzahi Fadida
• Re: Sector sizes in the kernel
  • From: Erik Mouw
• Re: How to get the network details through programming
  • From: Erik Mouw
• Re: Sector sizes in the kernel
  • From: burns . ethan
• Re: Sector sizes in the kernel
  • From: Tzahi Fadida
• Re: Sector sizes in the kernel
  • From: Avishay Traeger
• Re: Sector sizes in the kernel
  • From: Erik Mouw
• how to interpret the output of "cat /proc/1/maps"?
  • From: Robert P. J. Day
• Re: how to interpret the output of "cat /proc/1/maps"?
  • From: Daniel Cheng
• Execve system call
  • From: Neo Jia
• Re: how to interpret the output of "cat /proc/1/maps"?
  • From: Robert P. J. Day
• vmalloc - page tables
  • From: Pharaoh .
• atomic_read query
  • From: pradeep singh
• Re: vmalloc - page tables
  • From: Sandeep Sanjay Patil
• RE: vmalloc - page tables
  • From: Martyn Welch
• Re: vmalloc - page tables
  • From: Pharaoh .
• Re: How to identify a thread from task_struct
  • From: Pharaoh .
• Re: vmalloc - page tables
  • From: Sandeep Sanjay Patil
• Heap Randomization
  • From: vivek thakkar
• Re: I2C development on a PC
  • From: Ramagudi Naziir
• local_irq_save() and lost interrupts.
  • From: Ahmed S. Darwish
• You have a new PostCard from a friend
  • From: postcards . com
• mmaping device memory into userspace.
  • From: Daniel Rodrick
• Re: how to interpret the output of "cat /proc/1/maps"?
  • From: Prasad Joshi
• Re: How to get the network details through programming
  • From: Santosh Pradhan
• Re: How to get the network details through programming
  • From: Erik Mouw
• Isochronous USB implementation
  • From: Salvatore Benedetto
• problem with 2.6.20.3
  • From: kashif saeed
• out of memory problem
  • From: Deepak Joshi
• Re: How to get the network details through programming
  • From: Rajat Jain
• Re: out of memory problem
  • From: Matthias Kaehlcke
• general protection fault
  • From: Bernd Schubert
• Interface an LCD Epson S1D13506 to the ARM AT91RM9200
  • From: Queenie de Melo
• Re: mmaping device memory into userspace.
  • From: Erik Mouw
• Re: problem with 2.6.20.3
  • From: Erik Mouw
• Re: Interface an LCD Epson S1D13506 to the ARM AT91RM9200
  • From: Erik Mouw
• Re: general protection fault
  • From: Bernd Schubert
• Re: How to get the network details through programming
  • From: Santosh Pradhan
• Re: Isochronous USB implementation
  • From: Greg KH
• optimizing sendfile
  • From: Yaar
• Re: How to get the network details through programming
  • From: Erik Mouw
• Opening files in kernel mode
  • From: Andi Drebes
• Re: mmaping device memory into userspace.
  • From: Daniel Rodrick
• Policy Violation
  • From: Symantec_Mail_Security_for_SMTP
• how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Mansha Linux
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Rajat Jain
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Mansha Linux
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Rajat Jain
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: sandeep lahane
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Mansha Linux
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Matthias Kaehlcke
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Rajat Jain
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: anubhav rakshit
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Ahmed S. Darwish
• Re: Opening files in kernel mode
  • From: Erik Mouw
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Erik Mouw
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Rajat Jain
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: sandeep lahane
• Re: Opening files in kernel mode
  • From: Andi Drebes
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Sandeep Sanjay Patil
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: sandeep lahane
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Rajat Jain
• Automatically loading kernel modules at bootup
  • From: Daniel Rodrick
• regarding kernel preemption
  • From: Rick Brown
• fcntl v/s ioctl
  • From: Rick Brown
• Re: Automatically loading kernel modules at bootup
  • From: Matthias Kaehlcke
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Erik Mouw
• Re: Automatically loading kernel modules at bootup
  • From: Erik Mouw
• "struct file" - per process per file?
  • From: Rajat Jain
• Query regarding alloc_chrdev_region()
  • From: Rajat Jain
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Sandeep Sanjay Patil
• Patching the kernel and kernel 2.4.21 source code
  • From: Bizhan Gholikhamseh \(bgholikh\)
• RE: "struct file" - per process per file?
  • From: Gaurav Dhiman
• Re: "struct file" - per process per file?
  • From: Rajat Jain
• Re: Query regarding alloc_chrdev_region()
  • From: Rajat Jain
• Re: Query regarding alloc_chrdev_region()
  • From: Greg KH
• Re: Query regarding alloc_chrdev_region()
  • From: Greg KH
• Bootloader and Device driver queries
  • From: Queenie de Melo
• Re: fcntl v/s ioctl
  • From: Milind Arun Choudhary
• Re: Query regarding alloc_chrdev_region()
  • From: Rajat Jain
• Re: Query regarding alloc_chrdev_region()
  • From: Greg KH
• Re: "struct file" - per process per file?
  • From: black hole
• Re: Bootloader and Device driver queries
  • From: Milind Arun Choudhary
• Re: "struct file" - per process per file?
  • From: Rajat Jain
• Re: "struct file" - per process per file?
  • From: black hole
• Re: Patching the kernel and kernel 2.4.21 source code
  • From: Milind Arun Choudhary
• Re: "struct file" - per process per file?
  • From: Milind Arun Choudhary
• RE: Bootloader and Device driver queries
  • From: Martyn Welch
• RE: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Martyn Welch
• kernel compilation : newbie doubt
  • From: Rahul Ramasubramanian
• Re: kernel compilation : newbie doubt
  • From: Prathamesh Kini
• Re: kernel compilation : newbie doubt
  • From: Milind Arun Choudhary
• Re: kernel compilation : newbie doubt
  • From: topi
• Re: kernel compilation : newbie doubt
  • From: Erik Mouw
• Re: Automatically loading kernel modules at bootup
  • From: N Cocy
• Re: Automatically loading kernel modules at bootup
  • From: yogeshwar sonawane
• Re: regarding kernel preemption
  • From: Scott Wood
• is it just me, or is "systool" kind of lame?
  • From: Robert P. J. Day
• command line arguments
  • From: H. Charles Tang
• Should I use memory barriers with wait_event ?
  • From: John
• Hi all
  • From: cooper
• Re: Hi all
  • From: Anupam Kapoor