Linux Kernel Newbies

• Thread Index

• Re: local_irq_save()
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• RE: local_irq_save()
  • From: "Mukund JB." <mukundjb@xxxxxxxxxxxxxxxxxxxxx>
• upgrading the kernel !
  • From: "Onkar N Mahajan" <onkar.n.m@xxxxxxxxx>
• Re: Hashtable in the kernel
  • From: "Eddie Pettis" <pettis.eddie@xxxxxxxxx>
• mfn_x() in Xen
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: local_irq_save()
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: local_irq_save()
  • From: Guennadi Liakhovetski <gl@xxxxxxxxx>
• Re: local_irq_save()
  • From: Guennadi Liakhovetski <gl@xxxxxxxxx>
• Re: [Lustre-discuss] File system error !!
  • From: Oleg Drokin <green@xxxxxxxxxxxxx>
• Re: File system error !!
  • From: "Onkar N Mahajan" <onkar.n.m@xxxxxxxxx>
• Re: Out of tree kernel modules dependencies
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• File system error !!
  • From: "Onkar N Mahajan" <onkar.n.m@xxxxxxxxx>
• Re: About the sys_execve()
  • From: "R.wen" <rwen2012@xxxxxxxxx>
• Re: workqueues and serialization
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: visualization and jiffies
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: about the sys_execve()
  • From: Tetsuo Handa <penguin-newbie@xxxxxxxxxxxxxxxxxxx>
• Re: workqueues and serialization
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• query about virt.kernelnewbies.org
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: query about virt.kernelnewbies.org
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: query about virt.kernelnewbies.org
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: About the sys_execve()
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: Hashtable in the kernel
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• about the sys_execve()
  • From: "R.wen" <rwen2012@xxxxxxxxx>
• visualization and jiffies
  • From: "Eli Criffield" <elicriffield@xxxxxxxxx>
• Re: About the sys_execve()
  • From: "Neo Jia" <neojia@xxxxxxxxx>
• About the sys_execve()
  • From: "rwen2012" <rwen2012@xxxxxxxxx>
• Re: Hashtable in the kernel
  • From: "Eddie Pettis" <pettis.eddie@xxxxxxxxx>
• Re: Out of tree kernel modules dependencies
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: Automatic device creation with udev
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: Automatic device creation with udev
  • From: Sebastien Bourdeauducq <sebastien.bourdeauducq@xxxxxxxxx>
• Re: Automatic device creation with udev
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: Automatic device creation with udev
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: Out of tree kernel modules dependencies
  • From: Octavian Purdila <tavi@xxxxxxxxx>
• Re: Out of tree kernel modules dependencies
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: Out of tree kernel modules dependencies
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: Out of tree kernel modules dependencies
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: Zones and high memory.
  • From: "Ratnadeep Joshi" <ratn.josh@xxxxxxxxx>
• Re: Out of tree kernel modules dependencies
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Out of tree kernel modules dependencies
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Automatic device creation with udev
  • From: Sebastien Bourdeauducq <sebastien.bourdeauducq@xxxxxxxxx>
• Re: security_socket_create
  • From: "Ratnadeep Joshi" <ratn.josh@xxxxxxxxx>
• Re: vmalloc and page faults (was: memory descriptor and kernel threads)
  • From: "Ratnadeep Joshi" <ratn.josh@xxxxxxxxx>
• Re: security_socket_create
  • From: "Ratnadeep Joshi" <ratn.josh@xxxxxxxxx>
• Re: workqueues and serialization
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• security_socket_create
  • From: "Ashwin Rao" <ashwin.shirvanthe@xxxxxxxxx>
• Re: workqueues and serialization
  • From: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
• Re: linking problem
  • From: "Yogesh R. Tillu" <yogesh.tillu@xxxxxxxxxxxx>
• Re: linking problem
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: triggering dhcp from a network driver
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• linking problem
  • From: "igor pavlenko" <ipavlster@xxxxxxxxx>
• Re: spin_lock and bit_spin_lock
  • From: "igor pavlenko" <ipavlster@xxxxxxxxx>
• Re: triggering dhcp from a network driver
  • From: Cristian Zamfir <zamf@xxxxxxxxxxxxx>
• Re: local_irq_save()
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: local_irq_save()
  • From: Christian Boon <c.boon@xxxxxxxxxxxxxxxxxxxx>
• spin_lock and bit_spin_lock
  • From: "away.huang" <away.huang@xxxxxxxxx>
• Re: local_irq_save()
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: local_irq_save()
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• local_irq_save()
  • From: Christian Boon <c.boon@xxxxxxxxxxxxxxxxxxxx>
• Re: triggering dhcp from a network driver
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: vmalloc and page faults (was: memory descriptor and kernel threads)
  • From: "Adil Mujeeb" <mujeeb.adil@xxxxxxxxx>
• Re: vmalloc and page faults (was: memory descriptor and kernel threads)
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: make all{yes,mod}config expectations
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: workqueues and serialization
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: ext2's nobh mount option - what problem does it solve?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: make all{yes,mod}config expectations
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: workqueues and serialization
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: triggering dhcp from a network driver
  • From: Cristian Zamfir <zamf@xxxxxxxxxxxxx>
• Re: triggering dhcp from a network driver
  • From: Octavian Purdila <tavi@xxxxxxxxx>
• triggering dhcp from a network driver
  • From: Cristian Zamfir <zamf@xxxxxxxxxxxxx>
• Re: vmalloc and page faults (was: memory descriptor and kernel threads)
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• vmalloc and page faults (was: memory descriptor and kernel threads)
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: memory descriptor and kernel threads
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• Re: memory descriptor and kernel threads
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: about MBR/GPT partition style in linux
  • From: "Santosh Pradhan" <santosh.pradhan@xxxxxxxxx>
• Re: Linux-2.6.20
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: about MBR/GPT partition style in linux
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: about MBR/GPT partition style in linux
  • From: "Santosh Pradhan" <santosh.pradhan@xxxxxxxxx>
• Re: memory descriptor and kernel threads
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: memory descriptor and kernel threads
  • From: "Adil Mujeeb" <mujeeb.adil@xxxxxxxxx>
• Re: Using Relay FS for large Kernel buffer
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: memory descriptor and kernel threads
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: about MBR/GPT partition style in linux
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: memory descriptor and kernel threads
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: about MBR/GPT partition style in linux
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Using Relay FS for large Kernel buffer
  • From: mayank rana <mayank_rana_it@xxxxxxxxxxx>
• about MBR/GPT partition style in linux
  • From: "Santosh Pradhan" <santosh.pradhan@xxxxxxxxx>
• Re: what is the 'gso'?
  • From: "Anupam Kapoor" <anupam.kapoor@xxxxxxxxx>
• Re: memory descriptor and kernel threads
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• make all{yes,mod}config expectations
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• memory descriptor and kernel threads
  • From: "Adil Mujeeb" <mujeeb.adil@xxxxxxxxx>
• Re: what is the 'gso'?
  • From: "R.wen" <rwen2012@xxxxxxxxx>
• Re: what is the 'gso'?
  • From: Octavian Purdila <tavi@xxxxxxxxx>
• Re: what is the 'gso'?
  • From: "Anupam Kapoor" <anupam.kapoor@xxxxxxxxx>
• what is the 'gso'?
  • From: "R.wen" <rwen2012@xxxxxxxxx>
• Re: kernelnewbies Digest V7 #96
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: what does the 'tso' mean in the networking subsystem?
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: what does the 'tso' mean in the networking subsystem?
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• Re: about the tcp_sendpage()
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: linux 2.2, dentry cache question.
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Zones and high memory.
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: Zones and high memory.
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• workqueues and serialization
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• linux 2.2, dentry cache question.
  • From: Pawel <paulino90@xxxxxxxxx>
• Re: kgdb for 2.6.18 (Fedora core 6)
  • From: "Fawad Lateef" <fawadlateef@xxxxxxxxx>
• Re: Writing kernel API examples
  • From: "black hole" <neyrith@xxxxxxxxx>
• Re: about the tcp_sendpage()
  • From: "R.wen" <rwen2012@xxxxxxxxx>
• Linux-2.6.20
  • From: Hemanth Kumar <hemwire@xxxxxxxxxxx>
• Re: what does the 'tso' mean in the networking subsystem?
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: virtual address to vma address
  • From: "yogeshwar sonawane" <yogyas@xxxxxxxxx>
• Re: about the tcp_sendpage()
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• what does the 'tso' mean in the networking subsystem?
  • From: "rwen2012" <rwen2012@xxxxxxxxx>
• about the tcp_sendpage()
  • From: "rwen2012" <rwen2012@xxxxxxxxx>
• Re: Tracing page cache
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• Re: Writing kernel API examples
  • From: "Shakthi Kannan" <shakthimaan@xxxxxxxxx>
• Re: Question regarding physical memory access
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Question regarding physical memory access
  • From: "Jesús Velazquez" <jesus.velazquez@xxxxxxxxx>
• Re: Writing kernel API examples
  • From: Dinesh <dbhat@xxxxxxxxx>
• Writing kernel API examples
  • From: "black hole" <neyrith@xxxxxxxxx>
• Re: kgdb for 2.6.18 (Fedora core 6)
  • From: Ahmed A <ahmedcali@xxxxxxxxx>
• Tracing page cache
  • From: Seongsu Lee <senux@xxxxxxxxx>
• Re: kgdb for 2.6.18 (Fedora core 6)
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• kgdb for 2.6.18 (Fedora core 6)
  • From: Ahmed A <ahmedcali@xxxxxxxxx>
• Re: Zones and high memory.
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: Zones and high memory.
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• Re: virtual address to vma address
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: Zones and high memory.
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Zones and high memory.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: Different types of Address Types.
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: virtual address to vma address
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: virtual address to vma address
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: virtual address to vma address
  • From: "yogeshwar sonawane" <yogyas@xxxxxxxxx>
• Re: Setting Different Hardware modes
  • From: pradeep pradeep <asnvpradeep@xxxxxxxxx>
• Re: Different types of Address Types.
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Different types of Address Types.
  • From: Shreyansh <shreyansh.jain@xxxxxxxxx>
• Re: Different types of Address Types.
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: Different types of Address Types.
  • From: Shreyansh <shreyansh.jain@xxxxxxxxx>
• Re: Accessing USB Device configured with more than one Configuration
  • From: Greg KH <greg@xxxxxxxxx>
• Accessing USB Device configured with more than one Configuration
  • From: mayank rana <mayank_rana_it@xxxxxxxxxxx>
• Re: virtual address to vma address
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: Different types of Address Types.
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: ioctl timeouts
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• Re: usb major and minor number?
  • From: Greg KH <greg@xxxxxxxxx>
• ioctl timeouts
  • From: Russell <russell.sloan@xxxxxxxxxxxxxxx>
• [KJ]use mutex instead of a binary semaphore
  • From: Milind Arun Choudhary <milindchoudhary@xxxxxxxxx>
• Re: doubt about the 3-way handshake
  • From: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
• Re: virtual address to vma address
  • From: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
• Re: Different types of Address Types.
  • From: "Adil Mujeeb" <mujeeb.adil@xxxxxxxxx>
• Re: Confusion regarding GDT and PGD
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• 2 small git questions
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: Different types of Address Types.
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Setting Different Hardware modes
  • From: pradeep pradeep <asnvpradeep@xxxxxxxxx>
• Re: Confusion regarding GDT and PGD
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Different types of Address Types.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Confusion regarding GDT and PGD
  • From: "Leonidas ." <leonidas137@xxxxxxxxx>
• Re: virtual address to vma address
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Re: Hashtable in the kernel
  • From: Tzahi Fadida <Tzahi.ML@xxxxxxxxx>
• Re: virtual address to vma address
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• doubt about the 3-way handshake
  • From: "R.wen" <rwen2012@xxxxxxxxx>
• Re: Effect of the 'noapic' flag
  • From: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
• Re: virtual address to vma address
  • From: "srinivas bakki" <srinivas.bakki@xxxxxxxxx>
• Effect of the 'noapic' flag
  • From: "Pranav Peshwe" <pranavpeshwe@xxxxxxxxx>
• Re: Hashtable in the kernel
  • From: "Eddie Pettis" <pettis.eddie@xxxxxxxxx>
• Re: virtual address to vma address
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• Re: virtual address to vma address
  • From: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
• virtual address to vma address
  • From: Thomas Christensen <thomasc@xxxxxxxxxxx>
• usb major and minor number?
  • From: "Ashok kumar" <ashokmudalister@xxxxxxxxx>
• Re: USB probe for 3,1,2 USB HID mous device
  • From: Peter Fodrek <fodrek@xxxxxxxxxxxxxxxxx>
• configuring an environment to develop using uml
  • From: Rodrigo Baroni <baroni@xxxxxxxxxx>
• Re: Whitespace at end of lines in kernel source, et cetera
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: CIFS too slow on x86_64 machine.
  • From: Tetsuo Handa <penguin-newbie@xxxxxxxxxxxxxxxxxxx>
• Re: USB probe for 3,1,2 USB HID mous device
  • From: Jiri Kosina <jikos@xxxxxxxx>
• Re: USB probe for 3,1,2 USB HID mous device
  • From: Greg KH <greg@xxxxxxxxx>
• Re: USB probe for 3,1,2 USB HID mous device
  • From: Peter Fodrek <fodrek@xxxxxxxxxxxxxxxxx>
• Re: Whitespace at end of lines in kernel source, et cetera
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: Hashtable in the kernel
  • From: Tzahi Fadida <Tzahi.ML@xxxxxxxxx>
• Re: Whitespace at end of lines in kernel source, et cetera
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: USB probe for 3,1,2 USB HID mous device
  • From: Jiri Kosina <jikos@xxxxxxxx>
• Re: kernel aligned memory allocation
  • From: "venkatajagadeesh p" <cpvjagadeesh@xxxxxxxxx>
• Re: Hashtable in the kernel
  • From: "Eddie Pettis" <pettis.eddie@xxxxxxxxx>
• Re: Whether memory allocated by kmalloc/get_free_pages is swappable ?
  • From: "venkatajagadeesh p" <cpvjagadeesh@xxxxxxxxx>
• USB probe for 3,1,2 USB HID mous device
  • From: peto <fodrek@xxxxxxxxxxxxxxxxx>
• Re: Confusion about build cycle and vmlinux/bzImage (need uncompressed ELF image of built kernel)
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• kernel aligned memory allocation
  • From: "Nori, Sekhar" <nsekhar@xxxxxx>
• Re: Whether memory allocated by kmalloc/get_free_pages is swappable ?
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Whether memory allocated by kmalloc/get_free_pages is swappable ?
  • From: "yogeshwar sonawane" <yogyas@xxxxxxxxx>
• Re: Confusion about build cycle and vmlinux/bzImage (need uncompressed ELF image of built kernel)
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Reducing memory used by build
  • From: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
• Confusion about build cycle and vmlinux/bzImage (need uncompressed ELF image of built kernel)
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: gcc alternate keywords and kernel source
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• How to generate a human-readable byte order after running objdump?
  • From: "Neo Jia" <neojia@xxxxxxxxx>
• Re: Dispensing information.
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Dispensing information.
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Hashtable in the kernel
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Dispensing information.
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Dispensing information.
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: Dispensing information.
  • From: Greg KH <greg@xxxxxxxxx>
• Reducing memory used by build
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: Dispensing information.
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: Dispensing information.
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: unable to git pull linux kernel]
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Sleeping some disk
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Kernel space limitations
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Kernel space limitations
  • From: "venkatajagadeesh p" <cpvjagadeesh@xxxxxxxxx>
• Re: Dispensing information.
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• Re: Dispensing information.
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Dispensing information.
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Kernel space limitations
  • From: Tzahi Fadida <Tzahi.ML@xxxxxxxxx>
• Re: Kernel space limitations
  • From: "venkatajagadeesh p" <cpvjagadeesh@xxxxxxxxx>
• Re: Kernel space limitations
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Kernel space limitations
  • From: "Adil Mujeeb" <mujeeb.adil@xxxxxxxxx>
• unable to git pull linux kernel]
  • From: <surya.prabhakar@xxxxxxxxx>
• CMDA/GSM Dual Mode MOBILE
  • From: "sales@xxxxxxxx" <whb@xxxxxxxx>
• Re: Serial suspend for a few seconds?
  • From: "Dequan Yang" <wolfsnow33@xxxxxxxxx>
• Re: Kernel space limitations
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Sleeping some disk
  • From: "Luis Useche" <luis@xxxxxxxxxx>
• Kernel space limitations
  • From: "venkatajagadeesh p" <cpvjagadeesh@xxxxxxxxx>
• Re: Whitespace at end of lines in kernel source, et cetera
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: Serial suspend for a few seconds?
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• how raw sockets work.
  • From: "Ashwin Rao" <ashwin.shirvanthe@xxxxxxxxx>
• Whitespace at end of lines in kernel source, et cetera
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: Capturing Ethernet frames from userspace
  • From: "Parag N(पराग़)" <panemade@xxxxxxxxx>
• Re: recursive locks in linux
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: ISRs in shared IRQ
  • From: Matthias Kaehlcke <matthias.kaehlcke@xxxxxxxxx>
• Re: Capturing Ethernet frames from userspace
  • From: kanishk rastogi <kanishk_rastogi85@xxxxxxxxx>
• ISRs in shared IRQ
  • From: "Sikandar Khan" <sikandar032@xxxxxxxxx>
• Capturing Ethernet frames from userspace
  • From: "Shuveb Hussain" <shuveb@xxxxxxxxx>
• Serial suspend for a few seconds?
  • From: "Dequan Yang" <wolfsnow33@xxxxxxxxx>
• Re: daemon
  • From: "Milind Arun Choudhary" <milindchoudhary@xxxxxxxxx>
• Re: getting user name from uid
  • From: Kari Hurtta <hurtta+gmane@xxxxxxxxxxxx>
• Re: getting user name from uid
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: daemon
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: recursive locks in linux
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: recursive locks in linux
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: recursive locks in linux
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• 2Gb/2Gb VM Split 2.6.20
  • From: kashif saeed <kashif_linux@xxxxxxxxx>
• 2Gb/2Gb VM Split 2.6.20
  • From: kashif saeed <kashif_linux@xxxxxxxxx>
• RE: recursive locks in linux
  • From: "Gaurav Dhiman" <gaurav.dhiman@xxxxxxxxxxx>
• Re: [KJ] remove SPIN_LOCK_UNLOCKED
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• ext2's nobh mount option - what problem does it solve?
  • From: Kirk True <kirk@xxxxxxxxxxxxxxxx>
• ext2 - setting s_prealloc_blocks
  • From: Kirk True <kirk@xxxxxxxxxxxxxxxx>
• Re: recursive locks in linux
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• RE: daemon
  • From: "Srinivas G." <srinivasg@xxxxxxxxxxxxxxxxxxxxx>
• recursive locks in linux
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: ext3, BKL, journal replay, multiple non-bind mounts of same device
  • From: Andreas Dilger <adilger@xxxxxxxxxxxxx>
• Re: [KJ] remove SPIN_LOCK_UNLOCKED
  • From: "Milind Arun Choudhary" <milindchoudhary@xxxxxxxxx>
• Re: getting user name from uid
  • From: Kari Hurtta <hurtta+gmane@xxxxxxxxxxxx>
• ext3, BKL, journal replay, multiple non-bind mounts of same device
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Where do I find the equivalent of drivers/scsi/README.st
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• Re: [KJ] remove SPIN_LOCK_UNLOCKED
  • From: Matthew Wilcox <matthew@xxxxxx>
• Re: getting user name from uid
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: [KJ]remove SPIN_LOCK_UNLOCKED
  • From: Roland Dreier <rdreier@xxxxxxxxx>
• Re: [KJ]remove SPIN_LOCK_UNLOCKED
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: [KJ]remove SPIN_LOCK_UNLOCKED
  • From: Roland Dreier <rdreier@xxxxxxxxx>
• Re: [KJ]remove SPIN_LOCK_UNLOCKED
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [KJ]remove SPIN_LOCK_UNLOCKED
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• Re: [KJ]remove SPIN_LOCK_UNLOCKED
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: [KJ]remove SPIN_LOCK_UNLOCKED
  • From: Roland Dreier <rdreier@xxxxxxxxx>
• [KJ]remove SPIN_LOCK_UNLOCKED
  • From: Milind Arun Choudhary <milindchoudhary@xxxxxxxxx>
• Re: getting user name from uid
  • From: Kari Hurtta <hurtta+gmane@xxxxxxxxxxxx>
• Re: make oldconfig
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: make oldconfig
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• what's the rationale for checking for "__STDC__"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: LDD3 scull code doubt
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: make oldconfig
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: Difference between signal/ hardware interrupt/software interrupt ?
  • From: "vinay salotagi" <yogi.penguin@xxxxxxxxx>
• Re: bus addresses and physical address diference in bootloaders
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• gcc alternate keywords and kernel source
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• the address of local labels
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "Javi Roman" <javiroman@xxxxxxxxxxxxxxx>
• Re: the address of local labels
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• Re: LDD3 scull code doubt
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Difference between signal/ hardware interrupt/software interrupt ?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: LDD3 scull code doubt
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Difference between signal/ hardware interrupt/software interrupt ?
  • From: GAggarwal@xxxxxxxxxxxxxxxxxx
• Re: doubt about ZONE_HIMEM
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• Re: How to contribute ?
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• Re: make oldconfig
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: initial stack pointer setup (in head.S)
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: LDD3 scull code doubt
  • From: "Andy Dalton" <andy.dalton@xxxxxxxxx>
• Re: LDD3 scull code doubt
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• get_sb/fill_super and BKL (VFS mounting)
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• initial stack pointer setup (in head.S)
  • From: h h <harsh512@xxxxxxxxx>
• Re: identifying useless sanitized header files
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: identifying useless sanitized header files
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: getting user name from uid
  • From: Martin Mancuska <borg@xxxxxxx>
• Re: getting user name from uid
  • From: Daniel Cheng <gmane@xxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• copy_from_user() - executing twice to read the data from same pointers
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: pidmap
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: getting user name from uid
  • From: Tetsuo Handa <penguin-newbie@xxxxxxxxxxxxxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: Vivek Kutal <vivekutal@xxxxxxxxx>
• Re: doubt about ZONE_HIMEM
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• doubt about ZONE_HIMEM
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: LDD3 scull code doubt
  • From: "anubhav rakshit" <anubhavrocks@xxxxxxxxx>
• LDD3 scull code doubt
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: How to pass data from kernel to user space in system call?
  • From: Matthias Kaehlcke <matthias.kaehlcke@xxxxxxxxx>
• getting user name from uid
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• How to pass data from kernel to user space in system call?
  • From: "Neo Jia" <neojia@xxxxxxxxx>
• Re: Not Initialize the shrinker->list after kmalloc() in mm/vmscan.c(V2.6.12)?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• bus addresses and physical address diference in bootloaders
  • From: "Saumendra Dash" <Saumendra.Dash@xxxxxxxxxxxx>
• Re: make oldconfig
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Memory mapping with character device
  • From: "black hole" <neyrith@xxxxxxxxx>
• Re: identifying useless sanitized header files
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: identifying useless sanitized header files
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• identifying useless sanitized header files
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: what's the logistics behind "make headers_install"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: what's the logistics behind "make headers_install"?
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• what's the logistics behind "make headers_install"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• pidmap
  • From: ninjaboy <n0b0dyn1nj4@xxxxxxxxx>
• Re: just want to clarify the various combinations for creating /proc files
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• just want to clarify the various combinations for creating /proc files
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Packed/padded structs and pointer arithmetic
  • From: Octavian Purdila <tavi@xxxxxxxxx>
• Re: Packed/padded structs and pointer arithmetic
  • From: Rene Herman <rene.herman@xxxxxxxxx>
• Packed/padded structs and pointer arithmetic
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: how to build in kernel boot options?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: how to upgrade glibc ?
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• Re: glibc upgrade .
  • From: "Nelson Castillo" <nelsoneci@xxxxxxxxx>
• how to upgrade glibc ?
  • From: "Onkar N Mahajan" <onkar.n.m@xxxxxxxxx>
• glibc upgrade .
  • From: "Onkar N Mahajan" <onkar.n.m@xxxxxxxxx>
• Re: ramfs
  • From: Greg KH <greg@xxxxxxxxx>
• ramfs
  • From: "Ashok kumar" <ashokmudalister@xxxxxxxxx>
• Re: how to build in kernel boot options?
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Re: how to build in kernel boot options?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: how to build in kernel boot options?
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• Re: how to build in kernel boot options?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: how to build in kernel boot options?
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• Re: what means "voluntary kernel preemption"?
  • From: Rene Herman <rene.herman@xxxxxxxxx>
• Re: what means "voluntary kernel preemption"?
  • From: Rene Herman <rene.herman@xxxxxxxxx>
• how to build in kernel boot options?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: make oldconfig
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• Re: make oldconfig
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: Disk not fully utilized
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Disk not fully utilized
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: what means "voluntary kernel preemption"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• what means "voluntary kernel preemption"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: make oldconfig
  • From: Adrian Bunk <bunk@xxxxxxxxx>
• make oldconfig
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• set_rtc_mmss: can;t update from 14 to 59
  • From: "Tony Chung" <tchung@xxxxxxxxxxxxxxxxxxx>
• Re: dual license and GPL
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: How to contribute ?
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: dual license and GPL
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• How to contribute ?
  • From: "Jérôme Hamm" <jh.linuxdev@xxxxxxxxx>
• Re: fram device driver
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: dual license and GPL
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• fram device driver
  • From: <krishna.vamsi@xxxxxxxxx>
• Re: dual license and GPL
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: dual license and GPL
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: dual license and GPL
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: dual license and GPL
  • From: duryodhan <duryodhan125@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: Mark Hounschell <markh@xxxxxxxxxx>
• Re: wireless NIC drivers
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: Kernel for only power-off purpose.
  • From: Tetsuo Handa <penguin-newbie@xxxxxxxxxxxxxxxxxxx>
• Re: dual license and GPL
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• dual license and GPL
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "Raseel Bhagat" <raseelbhagat@xxxxxxxxx>
• Re: wireless NIC drivers
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: daemon
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• daemon
  • From: Hemanth Kumar <hemwire@xxxxxxxxxxx>
• reader-writer spinlocks
  • From: "Rick Brown" <rick.brown.3@xxxxxxxxx>
• book opinion
  • From: "Roman Mashak" <mrv@xxxxxxxxxxxxx>
• Partial buffer_head acquisition
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: bootloader
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• bootloader
  • From: "Roman Mashak" <mrv@xxxxxxxxxxxxx>
• Re: wireless NIC drivers
  • From: "Roman Mashak" <mrv@xxxxxxxxxxxxx>
• amd64 address
  • From: ninjaboy <n0b0dyn1nj4@xxxxxxxxx>
• Re: cannot create sda16
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• cannot create sda16
  • From: Shriramana Sharma <samjnaa@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: Daniel Cheng <gmane@xxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "Rick Brown" <rick.brown.3@xxxxxxxxx>
• Re: Why is Linux not RTOS?
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Why is Linux not RTOS?
  • From: "Rick Brown" <rick.brown.3@xxxxxxxxx>
• Re: wireless NIC drivers
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• DMA memory allocation in bootloaders
  • From: "Saumendra Dash" <Saumendra.Dash@xxxxxxxxxxxx>
• Re: kernel stack problem
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: kernel stack problem
  • From: "anubhav rakshit" <anubhavrocks@xxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: "anubhav rakshit" <anubhavrocks@xxxxxxxxx>
• socket system call hook
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• RE: Need for a new spinlock API?
  • From: GAggarwal@xxxxxxxxxxxxxxxxxx
• Re: Need for a new spinlock API?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• RE: Need for a new spinlock API?
  • From: GAggarwal@xxxxxxxxxxxxxxxxxx
• Re: Need for a new spinlock API?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: kernel stack problem
  • From: Fabiano Ramos <fabiano.ramos@xxxxxxxxx>
• Re: kernel stack problem
  • From: Fabiano Ramos <fabiano.ramos@xxxxxxxxx>
• Re: kernel stack problem
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: kernel stack problem
  • From: Fabiano Ramos <fabiano.ramos@xxxxxxxxx>
• kernel stack problem
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: kernel zeroing of user space memory?
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Kernel for only power-off purpose.
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Kernel for only power-off purpose.
  • From: Tetsuo Handa <penguin-newbie@xxxxxxxxxxxxxxxxxxx>
• Re: libata
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: wireless NIC drivers
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: kernel zeroing of user space memory?
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: irq routine and i2c_transfer
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• irq routine and i2c_transfer
  • From: borasahin@xxxxxxxxxxx
• libata
  • From: Russell <russell.sloan@xxxxxxxxxxxxxxx>
• Re: can a malloc be *both* GFP_KERNEL and GFP_ATOMIC?
  • From: "black hole" <neyrith@xxxxxxxxx>
• wireless NIC drivers
  • From: "Roman Mashak" <mrv@xxxxxxxxxxxxx>
• bind and unix doamin sockets
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: How to deliberately dump a kernel stack?
  • From: "black hole" <neyrith@xxxxxxxxx>
• Re: "system calls", and a question of terminology
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: linux VFS and non-hierarchical filesystems?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: linux VFS and non-hierarchical filesystems?
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: "system calls", and a question of terminology
  • From: Fabiano Ramos <fabiano.ramos@xxxxxxxxx>
• Re: "system calls", and a question of terminology
  • From: Rene Herman <rene.herman@xxxxxxxxx>
• Re: command line arguments
  • From: "black hole" <neyrith@xxxxxxxxx>
• "system calls", and a question of terminology
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Memory mapping with character device
  • From: cooperyuan <cooperyuan@xxxxxxxxx>
• Re: linux VFS and non-hierarchical filesystems?
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Memory mapping with character device
  • From: "black hole" <neyrith@xxxxxxxxx>
• linux VFS and non-hierarchical filesystems?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• kernel zeroing of user space memory?
  • From: "Ryan MacArthur" <ryan.macarthur@xxxxxxxxx>
• Re: Hi all
  • From: "Anupam Kapoor" <anupam.kapoor@xxxxxxxxx>
• Hi all
  • From: "cooper" <cooperyuan@xxxxxxxxx>
• Should I use memory barriers with wait_event ?
  • From: John <jhnlmn@xxxxxxxxx>
• command line arguments
  • From: "H. Charles Tang" <huitang@xxxxxxxxxxxxxxxxxx>
• is it just me, or is "systool" kind of lame?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: regarding kernel preemption
  • From: Scott Wood <scottwood@xxxxxxxxxxxxx>
• Re: Automatically loading kernel modules at bootup
  • From: "yogeshwar sonawane" <yogyas@xxxxxxxxx>
• Re: Automatically loading kernel modules at bootup
  • From: "N Cocy" <novu3novrin@xxxxxxxxx>
• Re: kernel compilation : newbie doubt
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: kernel compilation : newbie doubt
  • From: topi <topi23@xxxxxxxxx>
• Re: kernel compilation : newbie doubt
  • From: "Milind Arun Choudhary" <milindchoudhary@xxxxxxxxx>
• Re: kernel compilation : newbie doubt
  • From: Prathamesh Kini <prathamesh.kini@xxxxxxx>
• kernel compilation : newbie doubt
  • From: "Rahul Ramasubramanian" <ramasubramanian.rahul@xxxxxxxxx>
• RE: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Martyn Welch" <martyn.welch@xxxxxxxxxxxxxx>
• RE: Bootloader and Device driver queries
  • From: "Martyn Welch" <martyn.welch@xxxxxxxxxxxxxx>
• Re: "struct file" - per process per file?
  • From: "Milind Arun Choudhary" <milindchoudhary@xxxxxxxxx>
• Re: Patching the kernel and kernel 2.4.21 source code
  • From: "Milind Arun Choudhary" <milindchoudhary@xxxxxxxxx>
• Re: "struct file" - per process per file?
  • From: "black hole" <neyrith@xxxxxxxxx>
• Re: Bootloader and Device driver queries
  • From: "Milind Arun Choudhary" <milindchoudhary@xxxxxxxxx>
• Re: "struct file" - per process per file?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: "struct file" - per process per file?
  • From: "black hole" <neyrith@xxxxxxxxx>
• Re: Query regarding alloc_chrdev_region()
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Query regarding alloc_chrdev_region()
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: fcntl v/s ioctl
  • From: "Milind Arun Choudhary" <milindchoudhary@xxxxxxxxx>
• Bootloader and Device driver queries
  • From: "Queenie de Melo" <queenie245@xxxxxxxxx>
• Re: Query regarding alloc_chrdev_region()
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Query regarding alloc_chrdev_region()
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Query regarding alloc_chrdev_region()
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: "struct file" - per process per file?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• RE: "struct file" - per process per file?
  • From: "Gaurav Dhiman" <gaurav.dhiman@xxxxxxxxxxx>
• Patching the kernel and kernel 2.4.21 source code
  • From: "Bizhan Gholikhamseh \(bgholikh\)" <bgholikh@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• Query regarding alloc_chrdev_region()
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• "struct file" - per process per file?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Automatically loading kernel modules at bootup
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Automatically loading kernel modules at bootup
  • From: Matthias Kaehlcke <matthias.kaehlcke@xxxxxxxxx>
• fcntl v/s ioctl
  • From: "Rick Brown" <rick.brown.3@xxxxxxxxx>
• regarding kernel preemption
  • From: "Rick Brown" <rick.brown.3@xxxxxxxxx>
• Automatically loading kernel modules at bootup
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• Re: Opening files in kernel mode
  • From: Andi Drebes <lists-receive@xxxxxxxxxxxxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Opening files in kernel mode
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "anubhav rakshit" <anubhavrocks@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: Matthias Kaehlcke <matthias.kaehlcke@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Mansha Linux" <mansha.linux@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Mansha Linux" <mansha.linux@xxxxxxxxx>
• Re: how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• how the interrupt handler(ISR) knows the source of interrupt ?
  • From: "Mansha Linux" <mansha.linux@xxxxxxxxx>
• Re: mmaping device memory into userspace.
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Opening files in kernel mode
  • From: Andi Drebes <webmaster@xxxxxxxxxxxxxxxxxxx>
• Re: How to get the network details through programming
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• optimizing sendfile
  • From: Yaar <yaar@xxxxxxxxx>
• Re: Isochronous USB implementation
  • From: Greg KH <greg@xxxxxxxxx>
• Re: How to get the network details through programming
  • From: "Santosh Pradhan" <santosh.pradhan@xxxxxxxxx>
• Re: general protection fault
  • From: Bernd Schubert <bschubert@xxxxxxxxx>
• Re: Interface an LCD Epson S1D13506 to the ARM AT91RM9200
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: problem with 2.6.20.3
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: mmaping device memory into userspace.
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Interface an LCD Epson S1D13506 to the ARM AT91RM9200
  • From: "Queenie de Melo" <queenie245@xxxxxxxxx>
• general protection fault
  • From: Bernd Schubert <bschubert@xxxxxxxxx>
• Re: out of memory problem
  • From: Matthias Kaehlcke <matthias.kaehlcke@xxxxxxxxx>
• Re: How to get the network details through programming
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• out of memory problem
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• problem with 2.6.20.3
  • From: kashif saeed <kashif_linux@xxxxxxxxx>
• Isochronous USB implementation
  • From: "Salvatore Benedetto" <emitrax@xxxxxxxxx>
• Re: How to get the network details through programming
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: How to get the network details through programming
  • From: "Santosh Pradhan" <santosh.pradhan@xxxxxxxxx>
• Re: how to interpret the output of "cat /proc/1/maps"?
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• mmaping device memory into userspace.
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• local_irq_save() and lost interrupts.
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: I2C development on a PC
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Heap Randomization
  • From: vivek thakkar <vivekthakkar123@xxxxxxxxx>
• Re: vmalloc - page tables
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• Re: How to identify a thread from task_struct
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• Re: vmalloc - page tables
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• RE: vmalloc - page tables
  • From: "Martyn Welch" <martyn.welch@xxxxxxxxxxxxxx>
• Re: vmalloc - page tables
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• atomic_read query
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• vmalloc - page tables
  • From: "Pharaoh ." <pharaoh137@xxxxxxxxx>
• Re: how to interpret the output of "cat /proc/1/maps"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Execve system call
  • From: "Neo Jia" <neojia@xxxxxxxxx>
• Re: how to interpret the output of "cat /proc/1/maps"?
  • From: Daniel Cheng <gmane@xxxxxxxx>
• how to interpret the output of "cat /proc/1/maps"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: burns.ethan@xxxxxxxxx
• Re: How to get the network details through programming
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: burns.ethan@xxxxxxxxx
• Re: ETXTBSY error
  • From: Daniel Cheng <gmane@xxxxxxxx>
• Re: Sector sizes in the kernel
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Latency of indirect block mapping in EXT3?
  • From: Seongsu Lee <senux@xxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• ETXTBSY error
  • From: "Manoj Awasthi" <lkml.manoj@xxxxxxxxx>
• Re: kernel source link
  • From: "Manoj Awasthi" <lkml.manoj@xxxxxxxxx>
• Optimal Block Size / Max Device Size
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• How to get the network details through programming
  • From: "Santosh Pradhan" <santosh.pradhan@xxxxxxxxx>
• Re: Help with writing device driver for RS-485 transceiver
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Sector sizes in the kernel
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• RE: Zero Initialized in BSS
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: meaning of kernel error messages
  • From: Bernd Schubert <bs@xxxxxxxxx>
• Re: can a malloc be *both* GFP_KERNEL and GFP_ATOMIC?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• RE: Zero Initialized in BSS
  • From: "Martyn Welch" <martyn.welch@xxxxxxxxxxxxxx>
• RE: OS Clock
  • From: "Martyn Welch" <martyn.welch@xxxxxxxxxxxxxx>
• Re: meaning of kernel error messages
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• meaning of kernel error messages
  • From: Bernd Schubert <bschubert@xxxxxxxxx>
• Re: RS232 pin controlling
  • From: Christoph Fritz <chris_honschu@xxxxxx>
• Re: what's the rationale behind kbuild "depends on m"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: what's the rationale behind kbuild "depends on m"?
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• can a malloc be *both* GFP_KERNEL and GFP_ATOMIC?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• what's the rationale behind kbuild "depends on m"?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Zero Initialized in BSS
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: identifying kernel version from code files
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• identifying kernel version from code files
  • From: "Nirmal Thacker" <thacker.nirmal@xxxxxxxxx>
• Re: Zero Initialized in BSS
  • From: Daniel Cheng <gmane@xxxxxxxx>
• Re: to get IP address of network interfaces from Kernel space.
  • From: "Cristian Tapus" <cristian.tapus@xxxxxxxxx>
• to get IP address of network interfaces from Kernel space.
  • From: "Bizhan Gholikhamseh \(bgholikh\)" <bgholikh@xxxxxxxxx>
• Re: Zero Initialized in BSS
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: Zero Initialized in BSS
  • From: "Neo Jia" <neojia@xxxxxxxxx>
• Zero Initialized in BSS
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: Best solution to experiment with kernel
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Sector sizes in the kernel
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• killing NPTL threads
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: Best solution to experiment with kernel
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: need for 3G/1G split
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: OS Clock
  • From: "Bithika Khargharia" <bithika@xxxxxxxxx>
• Re: module registers
  • From: ninjaboy <n0b0dyn1nj4@xxxxxxxxx>
• Re: core file generation
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: module registers
  • From: Venkatesh Srinivas <me@xxxxxxxxxxx>
• Re: module registers
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• module registers
  • From: ninjaboy <n0b0dyn1nj4@xxxxxxxxx>
• Re: confusing passage in Doc.../mutex-design.txt
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: confusing passage in Doc.../mutex-design.txt
  • From: matze <matze@xxxxxxxxxx>
• confusing passage in Doc.../mutex-design.txt
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Help with writing device driver for RS-485 transceiver
  • From: "WANG Zhen" <zhenwang0115@xxxxxxxxx>
• Re: Help with writing device driver for RS-485 transceiver
  • From: "WANG Zhen" <zhenwang0115@xxxxxxxxx>
• core file generation
  • From: "Ming Chen" <tomingchen@xxxxxxxxx>
• Re: Help with writing device driver for RS-485 transceiver
  • From: Christian Boon <c.boon@xxxxxxxxxxxxxxxxxxxx>
• Re: Help with writing device driver for RS-485 transceiver
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: OS Clock
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Help with writing device driver for RS-485 transceiver
  • From: "WANG Zhen" <zhenwang0115@xxxxxxxxx>
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Help with understanding PCI
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Help with understanding PCI
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• RE: RS232 pin controlling
  • From: "Martyn Welch" <martyn.welch@xxxxxxxxxxxxxx>
• RE: OS Clock
  • From: "Martyn Welch" <martyn.welch@xxxxxxxxxxxxxx>
• RE: Help with understanding PCI
  • From: "Martyn Welch" <martyn.welch@xxxxxxxxxxxxxx>
• eth_type_trans and protocol field query
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: cpu and memory usage
  • From: mayank rana <mayank_rana_it@xxxxxxxxxxx>
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Greg KH <greg@xxxxxxxxx>
• RE: Help with understanding PCI
  • From: <krishna.vamsi@xxxxxxxxx>
• OS Clock
  • From: "Bithika Khargharia" <bithika@xxxxxxxxx>
• Re: cpu and memory usage
  • From: "Neependra Khare" <neependra.khare@xxxxxxxxx>
• cpu and memory usage
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: Help with understanding PCI
  • From: "Shawn Bohrer" <shawn.bohrer@xxxxxxxxx>
• Re: Help with understanding PCI
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: Greg KH <greg@xxxxxxxxx>
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• any reason alloc_chrdev_region() limits itself to major num of 255?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Help with understanding PCI
  • From: Greg KH <greg@xxxxxxxxx>
• Re: Help with understanding PCI
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: __devinit, __meminit, __cpuinit, etc.
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• __devinit, __meminit, __cpuinit, etc.
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Help with understanding PCI
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• RE: design with spin_locks
  • From: "Ajay Singh \(ajaysi\)" <ajaysi@xxxxxxxxx>
• Re: Help with understanding PCI
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Help with understanding PCI
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• design with spin_locks
  • From: "anubhav rakshit" <anubhavrocks@xxxxxxxxx>
• Help with understanding PCI
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: need for 3G/1G split
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: need for 3G/1G split
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: need for 3G/1G split
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• RE: Need for a new spinlock API?
  • From: "Ajay Singh \(ajaysi\)" <ajaysi@xxxxxxxxx>
• Re: kernel start addr
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• RE: Need for a new spinlock API?
  • From: "Ajay Singh \(ajaysi\)" <ajaysi@xxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• RS232 pin controlling
  • From: "Felipe Balbi" <felipebalbi@xxxxxxxxxxxxxxxxxxxxx>
• Re: kernel source link
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: Really newbie ;-)
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Best solution to experiment with kernel
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: Best solution to experiment with kernel
  • From: "Nelson Castillo" <nelsoneci@xxxxxxxxx>
• Re: Best solution to experiment with kernel
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: Best solution to experiment with kernel
  • From: matze <matze@xxxxxxxxxx>
• Best solution to experiment with kernel
  • From: "Fernando Apesteguía" <fernando.apesteguia@xxxxxxxxx>
• Re: need for 3G/1G split
  • From: Vivek <vivekutal@xxxxxxxxx>
• Re: kernel source link
  • From: "Neependra Khare" <neependra.khare@xxxxxxxxx>
• Re: kernel source link
  • From: "Jesper Juhl" <jesper.juhl@xxxxxxxxx>
• kernel source link
  • From: "Manoj Awasthi" <lkml.manoj@xxxxxxxxx>
• Re: doubt about VMA struct
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• decoding oops.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: Need for a new spinlock API?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: need for mmap?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• directio for device memory
  • From: "Ameya Mitragotri" <ameya.mitragotri@xxxxxxxxx>
• Re: doubt about VMA struct
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: kernel preemption
  • From: "Mansha Linux" <mansha.linux@xxxxxxxxx>
• Re: doubt about VMA struct
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• need for 3G/1G split
  • From: "Rick Brown" <rick.brown.3@xxxxxxxxx>
• kernel preemption
  • From: "Rick Brown" <rick.brown.3@xxxxxxxxx>
• need for mmap?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: doubt about VMA struct
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Need for a new spinlock API?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: kernel start addr
  • From: ninjaboy <n0b0dyn1nj4@xxxxxxxxx>
• Re: kernel start addr
  • From: Thomas Petazzoni <thomas.petazzoni@xxxxxxxx>
• Re: query related to different architectures
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• query related to different architectures
  • From: "Rick Brown" <rick.brown.3@xxxxxxxxx>
• Re: doubt about VMA struct
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: doubt about VMA struct
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: Doubt regarding memory
  • From: "Mansha Linux" <mansha.linux@xxxxxxxxx>
• Re: recursive locking in linux?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: kernel crash dump anomaly (scheduling in interrupt)
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• Re: doubt about VMA struct
  • From: "sandeep lahane" <sandeep.lahane@xxxxxxxxx>
• doubt about VMA struct
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• kernel start addr
  • From: ninjaboy <n0b0dyn1nj4@xxxxxxxxx>
• Re: ACL --- chmod and setfacl
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Emitting an ignore_int() handled interrupt and system response
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: ACL --- chmod and setfacl
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• ACL --- chmod and setfacl
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: Emitting an ignore_int() handled interrupt and system response
  • From: Daniel Cheng <gmane@xxxxxxxx>
• Re: help me to understand __atomic_hash()
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: help me to understand __atomic_hash()
  • From: topi <topi23@xxxxxxxxx>
• Re: Compiling 2.6.20-mm2 for Sparc64
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Emitting an ignore_int() handled interrupt and system response
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: recursive locking in linux?
  • From: matze <matze@xxxxxxxxxx>
• Allocated kernel memory not page aligned??...
  • From: "Kris van Rens" <krisvanrens.list@xxxxxxxxx>
• Re: recursive locking in linux?
  • From: matze <matze@xxxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: "pradeep singh" <2500.pradeep@xxxxxxxxx>
• Re: recursive locking in linux?
  • From: matze <matze@xxxxxxxxxx>
• help me to understand __atomic_hash()
  • From: "N Cocy" <novu3novrin@xxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: Understanding PCI
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: Momchil Velikov <chill@xxxxxxxxx>
• Re: recursive locking in linux?
  • From: Momchil Velikov <chill@xxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Received a panic while closing the file.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: how much of the kernel address space is used for virtual addresses?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: how much of the kernel address space is used for virtual addresses?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: recursive locking in linux?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: Emitting an ignore_int() handled interrupt and system response
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: how much of the kernel address space is used for virtual addresses?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• Re: recursive locking in linux?
  • From: "Daniel Rodrick" <daniel.rodrick@xxxxxxxxx>
• kernel crash dump anomaly (scheduling in interrupt)
  • From: "railroad seeker" <railroad.seeker@xxxxxxxxx>
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Emitting an ignore_int() handled interrupt and system response
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• how much of the kernel address space is used for virtual addresses?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Compiling 2.6.20-mm2 for Sparc64
  • From: Alexander Surma <alexander.surma@xxxxxx>
• Re: recursive locking in linux?
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Direct VFS/SB Access and Private Submounting
  • From: "John Anthony Kazos Jr." <jakj@xxxxxxxxxxx>
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Re: How to keep track of socket close()?
  • From: "Ye ilho" <iy2110@xxxxxxxxxxxx>
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: "Mulyadi Santosa" <mulyadi.santosa@xxxxxxxxx>
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• recursive locking in linux?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: glossary for gcc attributes used by kernel?
  • From: "Przemek Lib" <an.przemek@xxxxxxxxx>
• Understanding PCI
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• How to keep track of socket close()?
  • From: "Ye ilho" <iy2110@xxxxxxxxxxxx>
• Re: ERR_PTR and PTR_ERR
  • From: Ming Zhang <blackmagic02881@xxxxxxxxx>
• Re: ERR_PTR and PTR_ERR
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: ERR_PTR and PTR_ERR
  • From: Ming Zhang <blackmagic02881@xxxxxxxxx>
• Re: ERR_PTR and PTR_ERR
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: ERR_PTR and PTR_ERR
  • From: Ming Zhang <blackmagic02881@xxxxxxxxx>
• Re: ERR_PTR and PTR_ERR
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: ERR_PTR and PTR_ERR
  • From: Ming Zhang <blackmagic02881@xxxxxxxxx>
• Re: irq routine and i2c_transfer
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: How to let INITRAMFS continue as root filesystem?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• How to let INITRAMFS continue as root filesystem?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: ERR_PTR and PTR_ERR
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: How to identify a thread from task_struct
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• doubt regarding kmalloc() in fs/super.c
  • From: "anand muttagi" <avmuttagi@xxxxxxxxx>
• Re: How to identify a thread from task_struct
  • From: Sandeep Sanjay Patil <psandeep.s@xxxxxxxxx>
• Re: i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: How to identify a thread from task_struct
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• irq routine and i2c_transfer
  • From: borasahin@xxxxxxxxxxx
• How to identify a thread from task_struct
  • From: "Irfan Habib" <irfan.habib@xxxxxxxxx>
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: Thierry Reding <thierry@xxxxxxxx>
• Re: Is UML patches available for 2.6.20 kernel?
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: system call for setfacl
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• i386: Why putting __USER_DS in kernel threads stack (%esp) ?
  • From: "Ahmed S. Darwish" <darwish.07@xxxxxxxxx>
• Is UML patches available for 2.6.20 kernel?
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• RE: system call for setfacl
  • From: "Ajay Singh \(ajaysi\)" <ajaysi@xxxxxxxxx>
• system call for setfacl
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: Rajendra <rajendra_mishra@xxxxxxxxxxxxx>
• ip_rt_ioctl woes
  • From: "lee nookx" <lnookx@xxxxxxxxxxxxxx>
• Re: How does boot loader tell the kernel, the location of initrd?
  • From: "Shakthi Kannan" <shakthimaan@xxxxxxxxx>
• How does boot loader tell the kernel, the location of initrd?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: class_device_create_file warnings during compilation
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: class_device_create_file warnings during compilation
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: class_device_create_file warnings during compilation
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• CIFS too slow on x86_64 machine.
  • From: penguin-newbie@xxxxxxxxxxxxxxxxxxx
• Re: class_device_create_file warnings during compilation
  • From: "Nish Aravamudan" <nish.aravamudan@xxxxxxxxx>
• Re: class_device_create_file warnings during compilation
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• class_device_create_file warnings during compilation
  • From: Dinesh <dbhat@xxxxxxxxx>
• Re: query related to APIC and kernel
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• query related to APIC and kernel
  • From: "Pradeep Singh, TLS-Chennai" <pradeep_s@xxxxxx>
• Re: How to find the pid of the a given process.
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: How to find the pid of the a given process.
  • From: Amol Lad <amol@xxxxxxxxxxxxxxxxxxx>
• Re: How to find the pid of the a given process.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: smp/non-smp kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: How to find the pid of the a given process.
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• ERR_PTR and PTR_ERR
  • From: Ming Zhang <blackmagic02881@xxxxxxxxx>
• Re: How to find the pid of the a given process.
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: How to find the pid of the a given process.
  • From: santosh dwivedi <dwivedi_iiita@xxxxxxxxx>
• Re: How to find the pid of the a given process.
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Different debugging styles (was: glossary for gcc attributes used by kernel?)
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Different debugging styles (was: glossary for gcc attributes used by kernel?)
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• How to find the pid of the a given process.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: Writing inode_operations->create() function.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: Writing inode_operations->create() function.
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: Writing inode_operations->create() function.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: Writing inode_operations->create() function.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: Writing inode_operations->create() function.
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: smp/non-smp kernel
  • From: "my linux" <my.linux.newbie@xxxxxxxxx>
• Re: GPIO interrupt on PC ?
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: Writing inode_operations->create() function.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: Writing inode_operations->create() function.
  • From: Avishay Traeger <atraeger@xxxxxxxxxxxxx>
• Re: Writing inode_operations->create() function.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Problem with IP defragmentation in 2.6 kernel
  • From: "Kanhu Rauta" <choiskanhu@xxxxxxxxx>
• Writing inode_operations->create() function.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• Re: glossary for gcc attributes used by kernel?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• RE: "u area" virtual address
  • From: "Ajay Singh \(ajaysi\)" <ajaysi@xxxxxxxxx>
• Re: notifiers to user space
  • From: Asim <asimkadav@xxxxxxxxx>
• Re: notifiers to user space
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: Block Async I/O
  • From: "Randy.Dunlap" <rdunlap@xxxxxxxxxxxx>
• Re: notifiers to user space
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: notifiers to user space
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: "u area" virtual address
  • From: "Abhijit Pawar" <abhijit.acp@xxxxxxxxx>
• RE: "u area" virtual address
  • From: "Ajay Singh \(ajaysi\)" <ajaysi@xxxxxxxxx>
• Block Async I/O
  • From: "Nirmal Thacker" <thacker.nirmal@xxxxxxxxx>
• Re: notifiers to user space
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• kmem_getpages() and High Memory
  • From: "Dong Feng" <middle.fengdong@xxxxxxxxx>
• Re: notifiers to user space
  • From: Himanshu Chauhan <hs.chauhan@xxxxxxxxx>
• Re: glossary for gcc attributes used by kernel?
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• Re: notifiers to user space
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: notifiers to user space
  • From: Asim <asimkadav@xxxxxxxxx>
• Re: notifiers to user space
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: notifiers to user space
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• notifiers to user space
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• "u area" virtual address
  • From: "Abhijit Pawar" <abhijit.acp@xxxxxxxxx>
• GPIO interrupt on PC ?
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• Re: glossary for gcc attributes used by kernel?
  • From: "Rajat Jain" <rajat.noida.india@xxxxxxxxx>
• Re: IP Defragmentation
  • From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
• glossary for gcc attributes used by kernel?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: dynamic allocation of devices and udev
  • From: Greg KH <greg@xxxxxxxxx>
• I2C and interrupts
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• dynamic allocation of devices and udev
  • From: Himanshu Chauhan <hs.chauhan@xxxxxxxxx>
• Problem with registering security structure.
  • From: "Prasad Joshi" <prasadjoshi124@xxxxxxxxx>
• I2C dilemma and lm_sensors
  • From: "Ramagudi Naziir" <naziirr@xxxxxxxxx>
• ping DOS avoidance?
  • From: "Luis Carlos Cobo Rus" <luisca@xxxxxxxxxxx>
• how does the architecture affect browsing code at lxr.linux.no?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: magic sysrq question
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• Re: magic sysrq question
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• Re: more than 65535 outbound connections
  • From: Bernd Petrovitsch <bernd@xxxxxxxxx>
• Re: magic sysrq question
  • From: "Mike Frysinger" <vapier.adi@xxxxxxxxx>
• hpet_test doesn't work
  • From: ninjaboy <n0b0dyn1nj4@xxxxxxxxx>
• Re: magic sysrq question
  • From: Randy Dunlap <rdunlap@xxxxxxxxxxxx>
• magic sysrq question
  • From: "Ye ilho" <iy2110@xxxxxxxxxxxx>
• Re: more than 65535 outbound connections
  • From: "Greg Freemyer" <greg.freemyer@xxxxxxxxx>
• Re: smp/non-smp kernel
  • From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
• Re: cpu info 64bit/32bit
  • From: Tzahi Fadida <Tzahi.ML2@xxxxxxxxx>
• Re: cpu info 64bit/32bit
  • From: "Sandeep Kumar" <sandeepksinha@xxxxxxxxx>
• Re: cpu info 64bit/32bit
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Re: cpu info 64bit/32bit
  • From: Martin Mancuska <borg@xxxxxxx>
• cpu info 64bit/32bit
  • From: Deepak Joshi <deepak_cins@xxxxxxxxxxx>
• Re: 2.4 kernel parameters of a N2200
  • From: Erik Mouw <mouw@xxxxxxxxxxxx>
• Fwd: more than 65535 outbound connections
  • From: Niklaus <niklaus@xxxxxxxxx>
• Re: Thread safe circular buffer.
  • From: Momchil Velikov <chill@xxxxxxxxx>
• more than 65535 outbound connections
  • From: Niklaus <niklaus@xxxxxxxxx>
• Re: smp/non-smp kernel
  • From: "my linux" <my.linux.newbie@xxxxxxxxx>