Mail Index

• Thread Index

• Re: do ext3 symlinks cost any data blocks?
  • From: Erik Mouw
• Building a packet in the driver
  • From: cool fire
• Please reply immediatly
  • From: Jossef Khabai
• Re: RFC: Writing Solaris Device Drivers in Java - OT
  • From: Scott Lovenberg
• Re: blktrace debugging: how to use it
  • From: Mulyadi Santosa
• how does opening a char device set the cdev pointer in the inode?
  • From: Robert P. J. Day
• Re: Question about linux paging mechanism
  • From: Wu Yu
• Re: Building a packet in the driver
  • From: Michael Blizek
• RFC: swaptrace tool
  • From: Peter Teoh
• Re: RFC: swaptrace tool
  • From: Mulyadi Santosa
• Re: RFC: swaptrace tool
  • From: Peter Chubb
• Important Notification To All Customers.
  • From: Lloyds TSB Bank Plc.
• Re: how does opening a char device set the cdev pointer in the inode?
  • From: Robert P. J. Day
• Re: how does opening a char device set the cdev pointer in the inode?
  • From: Matthias Kaehlcke
• Re: how does opening a char device set the cdev pointer in the inode?
  • From: Matthias Kaehlcke
• Re: how does opening a char device set the cdev pointer in the inode?
  • From: Robert P. J. Day
• Re: how does opening a char device set the cdev pointer in the inode?
  • From: Robert P. J. Day
• Re: how does opening a char device set the cdev pointer in the inode?
  • From: Matthias Kaehlcke
• Re: RFC: Writing Solaris Device Drivers in Java
  • From: Daniel Bonekeeper
• CNN/BBC's UnSeen Video Reports
  • From: Faiza Ali
• how to tell if my kernel is SMP enabled?
  • From: Robert P. J. Day
• Re: how to tell if my kernel is SMP enabled?
  • From: Michael Blizek
• RE: how to tell if my kernel is SMP enabled?
  • From: Rajat Jain
• RE: how to tell if my kernel is SMP enabled?
  • From: Robert P. J. Day
• SCSI drivers
  • From: Onkar
• Re: how to tell if my kernel is SMP enabled?
  • From: Daniel Bonekeeper
• Re: how to tell if my kernel is SMP enabled?
  • From: Frank Thieme
• Re: how to tell if my kernel is SMP enabled?
  • From: Scott Lovenberg
• Listing of emergency medicine physicians and more
  • From: Hensley P Leann
• Re: Urgent Attention!!!:
  • From: Faradin Ahmad
• Conferma Ricarica Carta Postepay
  • From: BancoPosteOnline
• Reader/writer semaphores
  • From: bhanu nani
• Re: Reader/writer semaphores
  • From: Fabio De Francesco
• Re: RFC: swaptrace tool
  • From: Mulyadi Santosa
• Re: how to tell if my kernel is SMP enabled?
  • From: Mulyadi Santosa
• Re: how to tell if my kernel is SMP enabled?
  • From: Peter Teoh
• Re: RFC: swaptrace tool
  • From: Peter Teoh
• Re: RFC: swaptrace tool
  • From: Scott Lovenberg
• An interesting read: Extending the Linux Page Table
  • From: Peter Teoh
• Re: RFC: swaptrace tool
  • From: Mulyadi Santosa
• Re: RFC: swaptrace tool
  • From: Mulyadi Santosa
• Re: SCSI drivers
  • From: Peter Teoh
• getting data from a pci driver
  • From: santosh sivaraj
• Re: getting data from a pci driver
  • From: Frank Thieme
• Re: RFC: swaptrace tool
  • From: Peter Teoh
• Re: SCSI drivers
  • From: Erik Mouw
• Re: MIssed interrupts
  • From: Peter Teoh
• Re: why set a timer to expire at the current value of "jiffies"?
  • From: Peter Teoh
• Re: RFC: swaptrace tool
  • From: Peter Teoh
• mGinger !!
  • From: itsmeash
• RE: getting data from a pci driver
  • From: Rajat Jain
• processes, threads and thread groups
  • From: Robert P. J. Day
• journal_remove_journal_head oops in bad area access
  • From: Roberto A. Foglietta
• Re: journal_remove_journal_head oops in bad area access
  • From: Razvan Deaconescu
• Re: journal_remove_journal_head oops in bad area access
  • From: Erik Mouw
• Re: Reader/writer semaphores
  • From: bhanu nani
• Re: processes, threads and thread groups
  • From: Mulyadi Santosa
• Re: journal_remove_journal_head oops in bad area access
  • From: Roberto A. Foglietta
• Re: journal_remove_journal_head oops in bad area access
  • From: Roberto A. Foglietta
• Re: Reader/writer semaphores
  • From: sahlot arvind
• Re: Reader/writer semaphores
  • From: Erik Mouw
• Re: processes, threads and thread groups
  • From: Robert P. J. Day
• Re: processes, threads and thread groups
  • From: Robert P. J. Day
• where is ZONE_HIGHMEM defined?
  • From: Robert P. J. Day
• Re: where is ZONE_HIGHMEM defined?
  • From: Robert P. J. Day
• the first in a series of memory management questions
  • From: Robert P. J. Day
• Re: the first in a series of memory management questions
  • From: Fernando Apesteguía
• Re: the first in a series of memory management questions
  • From: Robert P. J. Day
• Re: the first in a series of memory management questions
  • From: Robert P. J. Day
• Re: the first in a series of memory management questions
  • From: Adil Mujeeb
• Re: where is ZONE_HIGHMEM defined?
  • From: Johannes Weiner
• Re: the first in a series of memory management questions
  • From: Balaji Rao
• Re: Reader/writer semaphores
  • From: bhanu nani
• more mm issues: logical versus virtual addresses
  • From: Robert P. J. Day
• Re: journal_remove_journal_head oops in bad area access
  • From: Razvan Deaconescu
• Re: journal_remove_journal_head oops in bad area access
  • From: Roberto A. Foglietta
• Re: more mm issues: logical versus virtual addresses
  • From: Rene Herman
• Re: more mm issues: logical versus virtual addresses
  • From: Robert P. J. Day
• Re: more mm issues: logical versus virtual addresses
  • From: Rene Herman
• Re: where is ZONE_HIGHMEM defined?
  • From: Peter Teoh
• Re: Reader/writer semaphores
  • From: sahlot arvind
• For your reading pleasure: Filesystem Internals
  • From: Peter Teoh
• given a particular CONFIG_XXXX in the .config how do u find more information about it?
  • From: Peter Teoh
• MMU vs no-MMU
  • From: Peter Teoh
• task_struct cputime_t fields
  • From: Adil Mujeeb
• Re: more mm issues: logical versus virtual addresses
  • From: Vivek Kutal
• memory management hack to achieve desired memory map
  • From: Peter Teoh
• Re: memory management hack to achieve desired memory map
  • From: Scott Lovenberg
• process traversal versus thread traversal
  • From: Robert P. J. Day
• Re: Reader/writer semaphores
  • From: bhanu nani
• Re: process traversal versus thread traversal
  • From: Nikhil Talpallikar
• Re: process traversal versus thread traversal
  • From: Robert P. J. Day
• what's the purpose of the CLONE_PARENT flag?
  • From: Robert P. J. Day
• Re: Reader/writer semaphores
  • From: bhanu nani
• Re: For your reading pleasure: Filesystem Internals
  • From: Mulyadi Santosa
• Re: MMU vs no-MMU
  • From: Mulyadi Santosa
• Re: task_struct cputime_t fields
  • From: Mulyadi Santosa
• Re: For your reading pleasure: Filesystem Internals
  • From: Scott Lovenberg
• Newbies question regarding git
  • From: Manish Katiyar
• extX features
  • From: Manish Katiyar
• Re: For your reading pleasure: Filesystem Internals
  • From: Peter Teoh
• Re: Newbies question regarding git
  • From: Peter Teoh
• Re: MMU vs no-MMU
  • From: Peter Teoh
• C or C++
  • From: max
• Re: extX features
  • From: arshad hussain
• Re: Reader/writer semaphores
  • From: debian developer
• Re: C or C++
  • From: Pavan Kandepet
• dev_hold() and dev_put()
  • From: zhengda
• Re: RFC: swaptrace tool
  • From: KOSAKI Motohiro
• Re: RFC: swaptrace tool
  • From: KOSAKI Motohiro
• Re: For your reading pleasure: Filesystem Internals
  • From: Peter Teoh
• Re: Newbies question regarding git
  • From: Vegard Nossum
• Re: blktrace debugging: how to use it
  • From: Jens Axboe
• Problems implementing a software RAID driver
  • From: Razvan Deaconescu
• gfp_mask flags
  • From: Nikhil Talpallikar
• semaphore locks
  • From: Nikhil Talpallikar
• Re: RFC: swaptrace tool
  • From: KOSAKI Motohiro
• Re: blktrace debugging: how to use it
  • From: Peter Teoh
• Re: gfp_mask flags
  • From: Nikhil Talpallikar
• Re: extX features
  • From: Erik Mouw
• Re: Newbies question regarding git
  • From: Erik Mouw
• Re: Reader/writer semaphores
  • From: bhanu nani
• Re: semaphore locks
  • From: bhanu nani
• Re: semaphore locks
  • From: Michael Blizek
• Re: Reader/writer semaphores
  • From: sahlot arvind
• Re: Problems implementing a software RAID driver
  • From: Razvan Deaconescu
• where is the macro "_syscall0" defined?
  • From: Robert P. J. Day
• Re: where is the macro "_syscall0" defined?
  • From: Rene Herman
• Re: where is the macro "_syscall0" defined?
  • From: Robert P. J. Day
• System setup for kernel experimentation.
  • From: Marc Butler
• Re: System setup for kernel experimentation.
  • From: Jesper Juhl
• Re: benefits to likely() and unlikely()?
  • From: Peter Teoh
• RE: gfp_mask flags
  • From: Rajat Jain
• RE: semaphore locks
  • From: Rajat Jain
• Which branded laptop and configuration is better.
  • From: venkatram ajmeera
• how to add my own module in menconfig
  • From: Daniel Baluta
• a question about dev_hold() and dev_put()
  • From: zhengda
• Re: how to add my own module in menconfig
  • From: Robert P. J. Day
• Re: how to add my own module in menconfig
  • From: ANOOP
• VMAs and "offset"s?
  • From: Robert P. J. Day
• Re: VMAs and "offset"s?
  • From: Peter Kerpedjiev
• Re: VMAs and "offset"s?
  • From: Robert P. J. Day
• Re: VMAs and "offset"s?
  • From: Johannes Weiner
• Re: VMAs and "offset"s?
  • From: Peter Kerpedjiev
• Re: VMAs and "offset"s?
  • From: Robert P. J. Day
• Re: VMAs and "offset"s?
  • From: Peter Kerpedjiev
• Re: VMAs and "offset"s?
  • From: Johannes Weiner
• Working of spinlock_irqsave
  • From: bhanu nani
• Re: VMAs and "offset"s?
  • From: Peter Teoh
• Re: VMAs and "offset"s?
  • From: Peter Teoh
• Re: Working of spinlock_irqsave
  • From: bhanu nani
• Re: VMAs and "offset"s?
  • From: Peter Teoh
• Re: VMAs and "offset"s?
  • From: Mulyadi Santosa
• Ctrl-C does not stop a process
  • From: tomy
• Re: where is ZONE_HIGHMEM defined?
  • From: Kris van Rens
• Re: Ctrl-C does not stop a process
  • From: Erik Mouw
• Re: C or C++
  • From: Mohamed Thalib .H
• Re: VMAs and "offset"s?
  • From: Robert P. J. Day
• Re: VMAs and "offset"s?
  • From: Robert P. J. Day
• Re: VMAs and "offset"s?
  • From: Robert P. J. Day
• Re: Ctrl-C does not stop a process
  • From: subramanian R
• Re: VMAs and "offset"s?
  • From: Johannes Weiner
• RE: Working of spinlock_irqsave
  • From: Rajat Jain
• /proc/slab_allocators empty??
  • From: hinko.kocevar@xxxxxxxxxxxx
• Trouble with PCI Ethernet card
  • From: Thomas Häberle
• Re: Trouble with PCI Ethernet card
  • From: Dinesh Bhat
• Re: Working of spinlock_irqsave
  • From: bhanu nani
• Re: Ctrl-C does not stop a process
  • From: DigitalPig
• Re: Reader/writer semaphores
  • From: bhanu nani
• Re: VMAs and "offset"s?
  • From: Peter Teoh
• ATH5K driver issue
  • From: cool fire
• Re: Ctrl-C does not stop a process
  • From: Peter Teoh
• Re: benefits to likely() and unlikely()?
  • From: Peter Teoh
• kernel preemption does not work
  • From: bhanu nani
• Re: Trouble with PCI Ethernet card
  • From: Thomas Häberle
• RE: kernel preemption does not work
  • From: Rajat Jain
• RE: Working of spinlock_irqsave
  • From: Rajat Jain
• TCP minRTO-value
  • From: kristrev
• clone - CLONE_THREAD and CLONE_SIGHAND without CLONE_VM
  • From: black hole
• Re: TCP minRTO-value
  • From: Kristian Evensen
• Re: ATH5K driver issue
  • From: Brandon Philips
• Re: clone - CLONE_THREAD and CLONE_SIGHAND without CLONE_VM
  • From: Mulyadi Santosa
• Re: kernel preemption does not work
  • From: Mulyadi Santosa
• Re: TCP minRTO-value
  • From: Mulyadi Santosa
• Re: /proc/slab_allocators empty??
  • From: Peter Teoh
• Re: kernel preemption does not work
  • From: Peter Teoh
• usb_control_msg for devices without an OUT endpoint.
  • From: Ribamar Santarosa de Sousa
• Re: kernel preemption does not work
  • From: Scott Lovenberg
• Re: usb_control_msg for devices without an OUT endpoint.
  • From: Scott Lovenberg
• Re: kernel preemption does not work
  • From: Roberto A. Foglietta
• can i see a driver's registered *minor* number(s)?
  • From: Robert P. J. Day
• Re: can i see a driver's registered *minor* number(s)?
  • From: Mohamed Thalib .H
• Re: can i see a driver's registered *minor* number(s)?
  • From: Robert P. J. Day
• Re: clone - CLONE_THREAD and CLONE_SIGHAND without CLONE_VM
  • From: black hole
• Re: can i see a driver's registered *minor* number(s)?
  • From: Robert P. J. Day
• Re: can i see a driver's registered *minor* number(s)?
  • From: Robert P. J. Day
• Re: can i see a driver's registered *minor* number(s)?
  • From: Robert P. J. Day
• Re: can i see a driver's registered *minor* number(s)?
  • From: Rene Herman
• Re: can i see a driver's registered *minor* number(s)?
  • From: Rene Herman
• Re: can i see a driver's registered *minor* number(s)?
  • From: Rene Herman
• Re: can i see a driver's registered *minor* number(s)?
  • From: Robert P. J. Day
• Re: /proc/slab_allocators empty??
  • From: hinko.kocevar@xxxxxxxxxxxx
• Re: can i see a driver's registered *minor* number(s)?
  • From: Scott Lovenberg
• "struct inode" and internal "struct cdev*"?
  • From: Robert P. J. Day
• Re: kernel preemption does not work
  • From: Peter Teoh
• Re: kernel preemption does not work
  • From: bhanu nani
• Re: kernel preemption does not work
  • From: Patrick McManus
• Re: kernel preemption does not work
  • From: Mulyadi Santosa
• Re: kernel preemption does not work
  • From: Peter Teoh
• Re: kernel preemption does not work
  • From: Peter Teoh
• Working with kernel.
  • From: Tero Mäntyvaara
• Re: Working with kernel.
  • From: sahlot arvind
• Re: kernel preemption does not work
  • From: Patrick McManus
• Re: kernel preemption does not work
  • From: Peter Teoh
• Re: kernel preemption does not work
  • From: Patrick McManus
• Re: Working with kernel.
  • From: Scott Lovenberg
• Re: "struct inode" and internal "struct cdev*"?
  • From: Arvin Moezzi
• Way to monitor IP address change?...
  • From: Kris van Rens
• Re: Way to monitor IP address change?...
  • From: Mulyadi Santosa
• Re: kernel preemption does not work
  • From: Peter Teoh
• 4kb for kernel stack - what is that?
  • From: Peter Teoh
• How many kernel threads will be created
  • From: V . Ravikumar
• Re: 4kb for kernel stack - what is that?
  • From: Rene Herman
• Re: 4kb for kernel stack - what is that?
  • From: Robert P. J. Day
• Re: 4kb for kernel stack - what is that?
  • From: Rene Herman
• Re: Way to monitor IP address change?...
  • From: Patrick McManus
• Re: Working with kernel.
  • From: sahlot arvind
• Mail list archives
  • From: Daniel Baluta
• booting the kernel
  • From: Daniel Baluta
• times() is returning -1
  • From: tomy
• Question about PHONY
  • From: vichy
• Re: Mail list archives
  • From: Octavian Purdila
• Re: how to migrate from existing Ext3 (with/without LVM) filesystem on Fedora Core to XXX filesystem
  • From: Peter Teoh
• Re: Mail list archives
  • From: Rene Herman
• Re: 4kb for kernel stack - what is that?
  • From: Rene Herman
• how to migrate from existing Ext3 (with/without LVM) filesystem on Fedora Core to XXX filesystem
  • From: Peter Teoh
• Re: 4kb for kernel stack - what is that?
  • From: Peter Teoh
• Re: Working with kernel.
  • From: bhanu nani
• mdelay
  • From: Anil Kumar
• Re: times() is returning -1
  • From: Erik Mouw
• Re: Mail list archives
  • From: Erik Mouw
• Re: Way to monitor IP address change?...
  • From: Kris van Rens
• Re: Way to monitor IP address change?...
  • From: Ender . Dai
• Restarting interrupted processes
  • From: Christian Fischlin
• Re: mdelay
  • From: Greg Freemyer
• Re: How many kernel threads will be created
  • From: Michael Blizek
• global variables in modules
  • From: Bobby Holley
• Re: How many kernel threads will be created
  • From: Mulyadi Santosa
• How to come a process slept after schedule() call.
  • From: bhanu nani
• Re: How many kernel threads will be created
  • From: fisherman
• Re: How to come a process slept after schedule() call.
  • From: Mulyadi Santosa
• Re: global variables in modules
  • From: Mulyadi Santosa
• Re: Restarting interrupted processes
  • From: Mulyadi Santosa
• Re: 4kb for kernel stack - what is that?
  • From: Mulyadi Santosa
• Re: booting the kernel
  • From: Mulyadi Santosa
• Re: How many kernel threads will be created
  • From: ravikumar
• Doubt in differences between 2.4 and 2.6 kernel
  • From: Rahul Ramasubramanian
• Re: How many kernel threads will be created
  • From: Michael Blizek
• schedular..
  • From: shyam Burkule
• Re: How many kernel threads will be created
  • From: ravikumar
• Re: schedular..
  • From: Gaurav Aggarwal
• frame buffers probs
  • From: venkatram ajmeera
• Re: How many kernel threads will be created
  • From: sahlot arvind
• Re: schedular..
  • From: Peter Teoh
• Re: schedular..
  • From: Peter Teoh
• RFC: Self-snapshotting in Linux
  • From: Peter Teoh
• Re: RFC: Self-snapshotting in Linux
  • From: eric miao
• Re: kernel preemption does not work
  • From: Scott Lovenberg
• Re: schedular..
  • From: Mulyadi Santosa
• PCI->APIC IRQ transform
  • From: BJörn Lindqvist
• Config for frambuffers.
  • From: venkatram ajmeera
• Re: RFC: Self-snapshotting in Linux
  • From: Pranav Peshwe
• Re: frame buffers probs
  • From: Erik Mouw
• RE: schedular..
  • From: Rajat Jain
• Re: RFC: Self-snapshotting in Linux
  • From: Scott Lovenberg
• Re: given a particular CONFIG_XXXX in the .config how do u find more information about it?
  • From: Peter Teoh
• Re: RFC: Self-snapshotting in Linux
  • From: Pavel Machek
• Re: Config for frambuffers.
  • From: Yogesh Tillu
• regarding delayed ACK
  • From: Mulyadi Santosa
• Re: RFC: Self-snapshotting in Linux
  • From: Greg Freemyer
• Re: RFC: Self-snapshotting in Linux
  • From: Ben Nizette
• Linux NFS & RPC Implementation
  • From: Usman S. Ansari
• bad_page_fault oops
  • From: Roberto A. Foglietta
• RE: bad_page_fault oops
  • From: Gaurav Aggarwal
• memory allocation when calling kmalloc
  • From: Wang Yu
• memory allocation when allocating pages
  • From: Wang Yu
• Re: bad_page_fault oops
  • From: Mulyadi Santosa
• Re: memory allocation when allocating pages
  • From: Mulyadi Santosa
• RE: memory allocation when allocating pages
  • From: Rajat Jain
• Re: regarding delayed ACK
  • From: Michael Blizek
• Asserts in kernel
  • From: Mrunal Gawade
• Re: Asserts in kernel
  • From: Rene Herman
• Re: Asserts in kernel
  • From: Rik van Riel
• Re: regarding delayed ACK
  • From: Mulyadi Santosa
• suggest some projects/assignments.
  • From: V . Ravikumar
• Re: suggest some projects/assignments.
  • From: Anil Kumar
• Re: suggest some projects/assignments.
  • From: Mulyadi Santosa
• Re: regarding delayed ACK
  • From: Michael Blizek
• Re: suggest some projects/assignments.
  • From: Michael Blizek
• Re: suggest some projects/assignments.
  • From: V . Ravikumar
• Re: regarding delayed ACK
  • From: Mulyadi Santosa
• Re: Asserts in kernel
  • From: Adrian Bunk
• Re: suggest some projects/assignments.
  • From: Henrik Austad
• Re: suggest some projects/assignments.
  • From: Michael Blizek
• Linux kernel networking related
  • From: Onkar
• Re: Linux kernel networking related
  • From: Anupam Kapoor
• alloc_chrdev_region doubt
  • From: anubhav rakshit
• PAGE_SIZE query
  • From: Nikhil Talpallikar
• Re: PAGE_SIZE query
  • From: Daniel Baluta
• Re: PAGE_SIZE query
  • From: Nikhil Talpallikar
• Re: PAGE_SIZE query
  • From: Nikhil Talpallikar
• Re: Linux kernel networking related
  • From: Michael Blizek
• Re: PAGE_SIZE query
  • From: Michael Blizek
• Re: PAGE_SIZE query
  • From: Bernd Petrovitsch
• Re: PAGE_SIZE query
  • From: Luciano Rocha
• Re: PAGE_SIZE query
  • From: Nikhil Talpallikar
• where to look at userspace implementation of fork() and clone()?
  • From: Robert P. J. Day
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Michael Kerrisk
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Michael Kerrisk
• Re: PAGE_SIZE query
  • From: Nikhil Talpallikar
• Re: PAGE_SIZE query
  • From: Mrunal Gawade
• Re: PAGE_SIZE query
  • From: Mrunal Gawade
• Re: PAGE_SIZE query
  • From: Nikhil Talpallikar
• Re: booting the kernel
  • From: Mulyadi Santosa
• Linux Device Driver development
  • From: Balraj Dahiya
• Re: Linux Device Driver development
  • From: Kyle Spaans
• Re: Linux Device Driver development
  • From: Mulyadi Santosa
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Michael Kerrisk
• Re: where to look at userspace implementation of fork() and clone()?
  • From: sahlot arvind
• Re: booting the kernel
  • From: Shyamal Shukla
• i386 -> x86?
  • From: Rajat Jain
• Re: booting the kernel
  • From: Mulyadi Santosa
• Re: i386 -> x86?
  • From: Mulyadi Santosa
• Re: i386 -> x86?
  • From: Carlo Bertoldi
• IRQ_OFFSET
  • From: Saumendra Dash
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Robert P. J. Day
• Re: Linux Device Driver development
  • From: Philippe Seewer
• question about colon ":" usage in Bash
  • From: vichy
• Re: question about colon ":" usage in Bash
  • From: Kyle Spaans
• how to avoid copies without O_DIRECT?
  • From: Miles
• Re: how to avoid copies without O_DIRECT?
  • From: Mulyadi Santosa
• kmem_cache_create reclaim callback?
  • From: Venkatesh Srinivas
• Re: kmem_cache_create reclaim callback?
  • From: Rik van Riel
• __udivdiv3 undefined
  • From: Mrunal Gawade
• timerfd syscall
  • From: Anupam Kapoor
• Re: __udivdiv3 undefined
  • From: Mohamed Thalib .H
• Re: __udivdiv3 undefined
  • From: Denis Kirjanov
• Re: timerfd syscall
  • From: Matthias Kaehlcke
• Re: timerfd syscall
  • From: Mulyadi Santosa
• DMA
  • From: jeyram jadenthradevan
• Kernel panic in PCI driver
  • From: jasjit singh
• Re: Kernel panic in PCI driver
  • From: Mulyadi Santosa
• How to get deleted files inode from super block
  • From: Kathiresan, Lekshmanan
• Re: How to get deleted files inode from super block
  • From: Mulyadi Santosa
• RE: How to get deleted files inode from super block
  • From: Kathiresan, Lekshmanan
• Re: How to get deleted files inode from super block
  • From: Manish Katiyar
• Why two stacks per process?
  • From: sahlot arvind
• Re: timerfd syscall
  • From: Michael Kerrisk
• Re: Why two stacks per process?
  • From: dinesh bansal
• Re: Why two stacks per process?
  • From: Robert P. J. Day
• Re: Why two stacks per process?
  • From: sahlot arvind
• Re: How to get deleted files inode from super block
  • From: Arthur
• Re: Why two stacks per process?
  • From: Robert P. J. Day
• Re: How to get deleted files inode from super block
  • From: Scott Lovenberg
• Re: Why two stacks per process?
  • From: Michael Blizek
• Re: Why two stacks per process?
  • From: Patrick McManus
• Re: How to get deleted files inode from super block
  • From: Peter Teoh
• Re: Why two stacks per process?
  • From: sahlot arvind
• Re: timerfd syscall
  • From: Anupam Kapoor
• Re: Why two stacks per process?
  • From: Bernd Petrovitsch
• what happens when the kernel stack overflows?
  • From: Robert P. J. Day
• Re: Why two stacks per process?
  • From: Patrick McManus
• Re: How to get deleted files inode from super block
  • From: Peter Teoh
• Re: Why two stacks per process?
  • From: Peter Teoh
• Re: Why two stacks per process?
  • From: Michael Blizek
• Re: what happens when the kernel stack overflows?
  • From: Michael Blizek
• Re: Why two stacks per process?
  • From: Patrick McManus
• Re: Kernel panic in PCI driver
  • From: MRizavan Sipai
• Re: what happens when the kernel stack overflows?
  • From: Robert P. J. Day
• Re: Why two stacks per process?
  • From: Robert P. J. Day
• blocknumber to index conversion in ext2
  • From: Manish Katiyar
• Re: Why two stacks per process?
  • From: Bernd Petrovitsch
• how is the kernel boot-time param "printk.time" implemented?
  • From: Robert P. J. Day
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Michael Kerrisk
• how to calculate the journal-blocks when try to start a handle?
  • From: Payphone LIOU
• Re: how is the kernel boot-time param "printk.time" implemented?
  • From: Mulyadi Santosa
• Re: Why two stacks per process?
  • From: Peter Teoh
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Peter Teoh
• Re: how is the kernel boot-time param "printk.time" implemented?
  • From: Robert P. J. Day
• Re: Kernel panic in PCI driver
  • From: jasjit singh
• Re: how is the kernel boot-time param "printk.time" implemented?
  • From: Mulyadi Santosa
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Michael Kerrisk
• Help: Kernel Panic while booting up linux 2.6.24
  • From: Siddeswar Reddy
• Re: Help: Kernel Panic while booting up linux 2.6.24
  • From: Mulyadi Santosa
• Help: Kernel Panic while booting up linux 2.6.24
  • From: Siddeswar Reddy
• Re: how is the kernel boot-time param "printk.time" implemented?
  • From: Robert P. J. Day
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Peter Teoh
• Re: how is the kernel boot-time param "printk.time" implemented?
  • From: Mulyadi Santosa
• Question on flow of control at the time of interrupt.
  • From: sahlot arvind
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Michael Kerrisk
• Dynamic linking on Linux
  • From: Shyamal Shukla
• Re: Dynamic linking on Linux
  • From: Mulyadi Santosa
• Re: C or C++
  • From: Rune V. Sjoen
• Re: Help: Kernel Panic while booting up linux 2.6.24
  • From: Mulyadi Santosa
• Re: Dynamic linking on Linux
  • From: sahlot arvind
• Re: Question on flow of control at the time of interrupt.
  • From: sahlot arvind
• Re: Help: Kernel Panic while booting up linux 2.6.24
  • From: Siddeswar Reddy
• Re: Question on flow of control at the time of interrupt.
  • From: eric miao
• Re: Help: Kernel Panic while booting up linux 2.6.24
  • From: Mulyadi Santosa
• Re: what happens when the kernel stack overflows?
  • From: Rene Herman
• Re: Help: Kernel Panic while booting up linux 2.6.24
  • From: Siddeswar Reddy
• Re: DMA
  • From: Rene Herman
• Re: Dynamic linking on Linux
  • From: Erik Mouw
• Re: where to look at userspace implementation of fork() and clone()?
  • From: Peter Teoh
• Send me an SMS
  • From: Akshay Sumant
• what's the value of "MODULE_STACKSIZE"?
  • From: Robert P. J. Day
• Re: what's the value of "MODULE_STACKSIZE"?
  • From: Rene Herman
• Re: what's the value of "MODULE_STACKSIZE"?
  • From: Robert P. J. Day
• Re: what's the value of "MODULE_STACKSIZE"?
  • From: Rene Herman
• Re: what's the value of "MODULE_STACKSIZE"?
  • From: Robert P. J. Day
• CPU Utilization
  • From: Rafael Almeida
• Re: Question on flow of control at the time of interrupt.
  • From: Russell King - ARM Linux
• Re: __udivdiv3 undefined
  • From: Mrunal Gawade
• Linux kernel crash dump
  • From: Mrunal Gawade
• Re: CPU Utilization
  • From: Rene Herman
• Re: Question on flow of control at the time of interrupt.
  • From: sahlot arvind
• Re: Dynamic linking on Linux
  • From: Pranav Peshwe
• RE: Linux kernel crash dump
  • From: srinivas.ramana
• Re: Question on flow of control at the time of interrupt.
  • From: sahlot arvind
• Segmentation understanding problems
  • From: Andreas Leppert
• Re: Dynamic linking on Linux
  • From: Erik Mouw
• Re: Segmentation understanding problems
  • From: Rene Herman
• Automic posting of changes document?
  • From: Rene Herman
• Re: Automic posting of changes document?
  • From: Arthur
• Re: Automic posting of changes document?
  • From: Adrian Bunk
• Re: Automic posting of changes document?
  • From: Rene Herman
• Re: Automic posting of changes document?
  • From: Rene Herman
• Re: Automic posting of changes document?
  • From: Rene Herman
• Re: Automic posting of changes document?
  • From: Adrian Bunk
• Re: Segmentation understanding problems
  • From: Rene Herman
• Q on Linux Memory Management (page tables)
  • From: sahlot arvind
• Re: Q on Linux Memory Management (page tables)
  • From: sahlot arvind
• Re: Q on Linux Memory Management (page tables)
  • From: Robert P. J. Day
• Re: Q on Linux Memory Management (page tables)
  • From: Rene Herman
• Searching English version of kernelnewbies mailing list archives ??
  • From: William Case
• Re: Searching English version of kernelnewbies mailing list archives ??
  • From: Rene Herman
• Linux kernel primer VS understaing the linux kernel .. ur comments
  • From: Rahul Ramasubramanian
• Re: Searching English version of kernelnewbies mailing list archives ??
  • From: Arthur
• Re: Linux kernel primer VS understaing the linux kernel .. ur comments
  • From: Adrian Bunk
• Re: Linux kernel primer VS understaing the linux kernel .. ur comments
  • From: sahlot arvind
• Re: Searching English version of kernelnewbies mailing list archives ??
  • From: Michael Kerrisk
• Re: Question on flow of control at the time of interrupt.
  • From: sahlot arvind
• Q on Fix-mapped linear address
  • From: sahlot arvind
• Re: Q on Linux Memory Management (page tables)
  • From: Robert P. J. Day
• Re: "struct inode" and internal "struct cdev*"?
  • From: Robert P. J. Day
• Re: Linux kernel primer VS understaing the linux kernel .. ur comments
  • From: Pavan Kandepet
• viewing memory ??
  • From: William Case
• "struct page" and allocating high memory
  • From: Robert P. J. Day
• Re: viewing memory ??
  • From: Jesper Juhl
• easy question on MM and struct pages
  • From: Robert P. J. Day
• Re: viewing memory ??
  • From: William Case
• kernel crash dump utility
  • From: Mrunal Gawade
• Re: viewing memory ??
  • From: Vaughn Clinton
• Re: Q on Fix-mapped linear address
  • From: Mulyadi Santosa
• Re: Why two stacks per process?
  • From: Peter Teoh
• Re: timerfd syscall
  • From: Anupam Kapoor
• Documentation on SCSI Subsystems and Fibre Channel(FC) protocol
  • From: Balraj Dahiya
• Memory mapping confusion
  • From: Chetan Nanda
• Re: Q on Fix-mapped linear address
  • From: Mulyadi Santosa
• Re: Q on Fix-mapped linear address
  • From: sahlot arvind
• Zone Questions
  • From: Andreas Leppert
• Re: timerfd syscall
  • From: Michael Kerrisk
• about the virtual address space of processes
  • From: 李一
• Zone sizes with low memory
  • From: Andreas Leppert
• Re: timerfd syscall
  • From: Anupam Kapoor
• Re: timerfd syscall
  • From: Michael Kerrisk
• Re: Linux kernel crash dump
  • From: Bernhard Walle
• Re: Memory mapping confusion
  • From: Rene Herman
• RE: Zone sizes with low memory
  • From: Vaughn Clinton
• Re: about the virtual address space of processes
  • From: Rene Herman
• Re: Zone Questions
  • From: Rene Herman
• Re: about the virtual address space of processes
  • From: Rene Herman
• Re: about the virtual address space of processes
  • From: 李一
• Re: about the virtual address space of processes
  • From: 李一
• Re: about the virtual address space of processes
  • From: 李一
• Re: about the virtual address space of processes
  • From: Rene Herman
• Re: about the virtual address space of processes
  • From: Rene Herman
• Re: Zone Questions
  • From: Mulyadi Santosa
• Re: about the virtual address space of processes
  • From: 李一
• Re: about the virtual address space of processes
  • From: Rene Herman
• Re: about the virtual address space of processes
  • From: Mulyadi Santosa
• Re: about the virtual address space of processes
  • From: Scott Lovenberg
• Re: Zone sizes with low memory
  • From: Rene Herman
• Re: easy question on MM and struct pages
  • From: Rene Herman
• Re: usb_control_msg for devices without an OUT endpoint.
  • From: Ribamar Santarosa de Sousa
• Re: "struct page" and allocating high memory
  • From: Rene Herman
• Re: "struct page" and allocating high memory
  • From: Rene Herman
• Using tgid instead of pid in ext3_find_near()
  • From: Manish Katiyar
• Kernelnewbies list delays (Re: easy question on MM and struct pages)
  • From: Rene Herman
• Re: "struct page" and allocating high memory
  • From: Rene Herman
• Re: "struct page" and allocating high memory
  • From: Peter Teoh
• Re: Using tgid instead of pid in ext3_find_near()
  • From: Mulyadi Santosa
• Re: about the virtual address space of processes
  • From: Scott Lovenberg
• Re: Using tgid instead of pid in ext3_find_near()
  • From: Manish Katiyar
• Sysctl re-deprecated!
  • From: Scott Lovenberg
• Re: Sysctl re-deprecated!
  • From: Rene Herman
• Re: kernel crash dump utility
  • From: Peter Teoh
• 勇敢去做！！ ^.^a
  • From: jianqie17
• Re: Sysctl re-deprecated!
  • From: Scott Lovenberg
• Query on directly accessing physical memory from a kernel module
  • From: Arjun
• RE: Query on directly accessing physical memory from a kernel module
  • From: Rajat Jain
• Re: Query on directly accessing physical memory from a kernel module
  • From: Arjun
• Re: Query on directly accessing physical memory from a kernel module
  • From: Arn
• Re: Query on directly accessing physical memory from a kernel module
  • From: Arn
• Similar to Readahead for write access to ide devices
  • From: Bizhan Gholikhamseh (bgholikh)
• Re: Similar to Readahead for write access to ide devices
  • From: Rene Herman
• Re: Similar to Readahead for write access to ide devices
  • From: Greg Freemyer