Linux Kernel Newbies

• Thread Index

• Re: printk and kernel log
  • From: Augusto Mecking Caringi <augustocaringi@xxxxxxxxx>
• printk and kernel log
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Filesystem and files getting corrupted
  • From: Daniel Hilst Selli <danielhilst@xxxxxxxxx>
• File system query
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: High Latency during packet transmission
  • From: Michael Krysiak <mrk191@xxxxxxxxx>
• Re: High Latency during packet transmission
  • From: "Vaughn@MSN" <vclinton@xxxxxxx>
• High Latency during packet transmission
  • From: Michael Krysiak <mrk191@xxxxxxxxx>
• another couple questions regarding wait queues
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: some questions/oddities regarding "exclusive" wait queues
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: some questions/oddities regarding "exclusive" wait queues
  • From: Valdis.Kletnieks@xxxxxx
• some questions/oddities regarding "exclusive" wait queues
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: File system query
  • From: Valdis.Kletnieks@xxxxxx
• Re: File system query
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: File system query
  • From: Valdis.Kletnieks@xxxxxx
• Re: On creation of irq_desc and irq_data.
  • From: "Subhra S. Sarkar" <sarkar@xxxxxxxxxxxxx>
• Re: File system query
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: On creation of irq_desc and irq_data.
  • From: mind entropy <mindentropy@xxxxxxxxx>
• Re: linux segment
  • From: Baoquan He <baoquan.he@xxxxxxxxx>
• On creation of irq_desc and irq_data.
  • From: mind entropy <mindentropy@xxxxxxxxx>
• Re: linux segment
  • From: Fan Yang <lljyangfan@xxxxxxxxx>
• Re: linux segment
  • From: Baoquan He <baoquan.he@xxxxxxxxx>
• Re: File system query
  • From: Rohan Puri <rohan.puri15@xxxxxxxxx>
• Re: File System query
  • From: Rohan Puri <rohan.puri15@xxxxxxxxx>
• File system query
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• File System query
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: tcp window concept
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: tcp window concept
  • From: Valdis.Kletnieks@xxxxxx
• Re: tcp window concept
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• hibernation image size
  • From: arden jay <arden.jay@xxxxxxxxx>
• Re: Writing device drivers
  • From: Jonathan Paugh <jpaugh@xxxxxx>
• tcp window concept
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• Re: Sending an ICMP packet with ip_local_out
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Sending an ICMP packet with ip_local_out
  • From: Adel Qodmani <mpcadel@xxxxxxxxx>
• Re: File system Query
  • From: Valdis.Kletnieks@xxxxxx
• Re: File system Query
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: File system Query
  • From: Valdis.Kletnieks@xxxxxx
• File system Query
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: UDP max packet size
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• Re: UDP max packet size
  • From: Victor Buciuc <victor.buciuc@xxxxxxxxx>
• UDP max packet size
  • From: Pietro Paolini <pulsarpietro@xxxxxxx>
• Re: Writing device drivers
  • From: shampavman <shampavman.cg@xxxxxxxxx>
• Re: Writing device drivers
  • From: Victor Rodriguez <vm.rod25@xxxxxxxxx>
• Writing device drivers
  • From: shampavman <shampavman.cg@xxxxxxxxx>
• Re: forum spam filtering
  • From: Racz Zoli <racz.zoli@xxxxxxxxx>
• Re: forum spam filtering
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• forum spam filtering
  • From: Rik van Riel <riel@xxxxxxxxxxx>
• RE: [alsa-devel] USB audio Gadget - code 10 error
  • From: "Eamon Hayden" <eamon.hayden@xxxxxxxxxxxxxxxxxxx>
• Re: Fwd: Mounting issue
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• Re: kdb understanding
  • From: Rajat Sharma <fs.rajat@xxxxxxxxx>
• Read BIOS
  • From: Satya Prakash Prasad <satyaprakash.prasad@xxxxxxxxx>
• Re: Fwd: Mounting issue
  • From: tomy <tomy@xxxxxxxxxxxx>
• Re: Fwd: Mounting issue
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• kdb understanding
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• Fwd: Mounting issue
  • From: tomy <tomy@xxxxxxxxxxxx>
• Re: hi Where initializate structure of current?
  • From: Valdis.Kletnieks@xxxxxx
• hi Where initializate structure of current?
  • From: lx <lxlenovostar@xxxxxxxxx>
• Re: Alignment trap exception
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Alignment trap exception
  • From: Amit Mahadik <amitmahadik35@xxxxxxxxx>
• bonding balance-alb tons of null info packets.
  • From: Nitin Sharma <nitinics@xxxxxxxxx>
• Re: [alsa-devel] USB audio Gadget - code 10 error
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• RE: [alsa-devel] USB audio Gadget - code 10 error
  • From: "Eamon Hayden" <eamon.hayden@xxxxxxxxxxxxxxxxxxx>
• RE: [alsa-devel] USB audio Gadget - code 10 error
  • From: "Eamon Hayden" <eamon.hayden@xxxxxxxxxxxxxxxxxxx>
• Re: USB audio Gadget - code 10 error
  • From: anish singh <anish198519851985@xxxxxxxxx>
• USB audio Gadget - code 10 error
  • From: "Eamon Hayden" <eamon.hayden@xxxxxxxxxxxxxxxxxxx>
• Re: Why is that the write speed of DDR SDRAM are faster than the DDR2
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: assembly of packets
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• RE: assembly of packets
  • From: Craig Jackson <cjackson@xxxxxxxxxxxxx>
• Re: Clarifications on PFN_UP(x) macro
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Clarifications on PFN_UP(x) macro
  • From: stl <st.lambert02@xxxxxxxxx>
• Re: assembly of packets
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• RE: assembly of packets
  • From: Craig Jackson <cjackson@xxxxxxxxxxxxx>
• Re: Getting started on Linux Kernel Development
  • From: Valdis.Kletnieks@xxxxxx
• Re: assembly of packets
  • From: Valdis.Kletnieks@xxxxxx
• Re: tracing send and recv system call
  • From: Kristof Provost <kristof@xxxxxxxxxx>
• Ti am335x usb pll configuration
  • From: Jelle Sels <jellesels@xxxxxxxxx>
• assembly of packets
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• tracing send and recv system call
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• Why is that the write speed of DDR SDRAM are faster than the DDR2
  • From: "devendra.aaru" <devendra.aaru@xxxxxxxxx>
• Re: Source based routing
  • From: Jason Ball <jason@xxxxxxxx>
• Source based routing
  • From: Adel Qodmani <mpcadel@xxxxxxxxx>
• Re: Getting started on Linux Kernel Development
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: LTS and LTSI
  • From: Saqlain Abbas <saqlain.abbas.7@xxxxxxxxx>
• Install kernel headers
  • From: Parmenides <mobile.parmenides@xxxxxxxxx>
• Re: Getting started on Linux Kernel Development
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: Getting started on Linux Kernel Development
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• Getting started on Linux Kernel Development
  • From: Daniel Hamacher <danielhamacher.dh@xxxxxxxxx>
• Re: which function perform gso
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• which function perform gso
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• Re: Memory leaks in Samsung's kernel
  • From: Michał Nykiel <michak.ny@xxxxxxxxx>
• Re: Memory leaks in Samsung's kernel
  • From: Matthias Brugger <matthias.bgg@xxxxxxxxx>
• Re: Not able to get crash dump
  • From: Valdis.Kletnieks@xxxxxx
• Not able to get crash dump
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: File System Implementation
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: hi about C and asm
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• File System Implementation
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: abort when using memory returned by io_remap_pfn_range
  • From: Brian Magnuson <bmagnuson@xxxxxxxxxxxxxx>
• Re: [I2C] informations + advice about messages handling
  • From: "Mylene Josserand" <Mylene.Josserand@xxxxxxxxxxx>
• Re: hi about C and asm
  • From: Augusto Mecking Caringi <augustocaringi@xxxxxxxxx>
• hi about C and asm
  • From: lx <lxlenovostar@xxxxxxxxx>
• Memory leaks in Samsung's kernel
  • From: Michał Akaanonim <michak.ny@xxxxxxxxx>
• Re: c library wrapper function
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• c library wrapper function
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• Re: about ssh
  • From: Valdis.Kletnieks@xxxxxx
• about ssh
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• Re: Kernel 64bit
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: mss for tcp segment
  • From: Valdis.Kletnieks@xxxxxx
• Re: Fwd: dump utility[sorry for last spam, it was tab+enter]
  • From: Valdis.Kletnieks@xxxxxx
• Re: dump utility[sorry for last spam, it was tab+enter]
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: dump utility
  • From: SandeepKsinha <sandeepksinha@xxxxxxxxx>
• mss for tcp segment
  • From: Varun Sharma <vsdssd@xxxxxxxxx>
• Fwd: dump utility[sorry for last spam, it was tab+enter]
  • From: jack rule <jackrule.1985@xxxxxxxxx>
• dump utility
  • From: jack rule <jackrule.1985@xxxxxxxxx>
• zambezi/bulldozer support
  • From: "Littlefield, Tyler" <tyler@xxxxxxxxxxxxx>
• File System : Error Checking
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: lookup function return value in inode_operations
  • From: Rajat Sharma <fs.rajat@xxxxxxxxx>
• lookup function return value in inode_operations
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: what's best way for playing with kernel configurations and source code
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: hi Why is "can't find a register in class
  • From: Valdis.Kletnieks@xxxxxx
• RE: Kernel 64bit
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: hi Why is "can't find a register in class ‘AREG’ while reloading ‘asm’" ?
  • From: Rajat Sharma <fs.rajat@xxxxxxxxx>
• Re: File system implementation
  • From: Vineet Agarwal <checkout.vineet@xxxxxxxxx>
• hi Why is "can't find a register in class ‘AREG’ while reloading ‘asm’" ?
  • From: lx <lxlenovostar@xxxxxxxxx>
• Re: Kernel 64bit
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: what's best way for playing with kernel configurations and source code
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: File system implementation
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• what's best way for playing with kernel configurations and source code
  • From: "Alshamlan, Mohammad" <malsh002@xxxxxxx>
• Re: File system implementation
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Kernel 64bit
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: building a kernel from a mounted partition
  • From: Valdis.Kletnieks@xxxxxx
• Re: building a kernel from a mounted partition
  • From: Andy Johnson <johnsonzjo@xxxxxxxxx>
• Re: File System : Block Groups
  • From: Valdis.Kletnieks@xxxxxx
• File System : Block Groups
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Re: Kernel .config file overwritten
  • From: Valdis.Kletnieks@xxxxxx
• which kernel config creates /dev/usb ?
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: building a kernel from a mounted partition
  • From: Anand Moon <moon.linux@xxxxxxxxx>
• Re: Kernel .config file overwritten
  • From: "Lakshmipathi.G" <lakshmipathi.g@xxxxxxxxx>
• Re: Kernel .config file overwritten
  • From: Valdis.Kletnieks@xxxxxx
• Re: Kernel .config file overwritten
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: File System
  • From: Racz Zoli <racz.zoli@xxxxxxxxx>
• File system implementation
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• File System
  • From: Dibyayan Chakraborty <dib.coolguy@xxxxxxxxx>
• Kernel .config file overwritten
  • From: "Lakshmipathi.G" <lakshmipathi.g@xxxxxxxxx>
• abort when using memory returned by io_remap_pfn_range
  • From: Brian Magnuson <bmagnuson@xxxxxxxxxxxxxx>
• Re: CPU usage of particular process
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: building a kernel from a mounted partition
  • From: Andy Johnson <johnsonzjo@xxxxxxxxx>
• Re: Bootloader sequence with time prefix (Kernelnewbies Digest, Vol 30, Issue 24)
  • From: Lucas Rangit Magasweran <lucas.magasweran@xxxxxxxx>
• Re: building a kernel from a mounted partition
  • From: Valdis.Kletnieks@xxxxxx
• Re: [I2C] informations + advice about messages handling
  • From: anish singh <anish198519851985@xxxxxxxxx>
• RE: Kernel 64bit
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: [I2C] informations + advice about messages handling
  • From: "Mylene Josserand" <Mylene.Josserand@xxxxxxxxxxx>
• Re: [I2C] informations + advice about messages handling
  • From: "Mylene Josserand" <Mylene.Josserand@xxxxxxxxxxx>
• building a kernel from a mounted partition
  • From: Andy Johnson <johnsonzjo@xxxxxxxxx>
• Re: [I2C] informations + advice about messages handling
  • From: anish singh <anish198519851985@xxxxxxxxx>
• [I2C] informations + advice about messages handling
  • From: "Mylene Josserand" <Mylene.Josserand@xxxxxxxxxxx>
• Re: Kernel 64bit
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• Re: Kernel 64bit
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• RE: Kernel 64bit
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: Kernel 64bit
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• RE: Kernel 64bit
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: Kernel 64bit
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• Kernel 64bit
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• android older sdk version
  • From: Ben Wu <crayben@xxxxxxxx>
• android old source code
  • From: "Ben Wu" <2110150311@xxxxxxxxxxxxxxxx>
• Re: Reference material for x86-64 assembly on Linux
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Soft CPU Affinity
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Bootloader sequence with time prefix
  • From: Valdis.Kletnieks@xxxxxx
• CPU usage of particular process
  • From: Rahul Bedarkar <rpal143@xxxxxxxxx>
• Re: Bootloader sequence with time prefix
  • From: Dhyan <linuxdhyan@xxxxxxxxx>
• Re: Reference material for x86-64 assembly on Linux
  • From: Rajat Sharma <fs.rajat@xxxxxxxxx>
• Re: Reference material for x86-64 assembly on Linux
  • From: wannabehacker wb <wbhack3r@xxxxxxxxx>
• Re: Bootloader sequence with time prefix
  • From: Valdis.Kletnieks@xxxxxx
• Re: Bootloader sequence with time prefix
  • From: Dhyan <linuxdhyan@xxxxxxxxx>
• Re: Bootloader sequence with time prefix
  • From: Valdis.Kletnieks@xxxxxx
• Bootloader sequence with time prefix
  • From: Dhyan <linuxdhyan@xxxxxxxxx>
• Reference material for x86-64 assembly on Linux
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• Re: Analyzing Kernel call traces.
  • From: Peter Teoh <htmldeveloper@xxxxxxxxx>
• Re: select call takes more time than the given timeout
  • From: Victor Buciuc <victor.buciuc@xxxxxxxxx>
• select call takes more time than the given timeout
  • From: "devendra.aaru" <devendra.aaru@xxxxxxxxx>
• Re: Emulating cpu page protection in userspace
  • From: Venkatram Tummala <venkatram867@xxxxxxxxx>
• Re: Emulating cpu page protection in userspace
  • From: Arun KS <getarunks@xxxxxxxxx>
• Re: how to debug thread stuck in filemap_fault
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Emulating cpu page protection in userspace
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Emulating cpu page protection in userspace
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: how do i read a block
  • From: Shampavman <shampavman.cg@xxxxxxxxx>
• how to debug thread stuck in filemap_fault
  • From: shuang liu <l121282s@xxxxxxxxxxxx>
• Re: how do i read a block
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: how to debug oom killer errors
  • From: Prashant Shah <pshah.mumbai@xxxxxxxxx>
• Re: how do i read a block
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: how do i read a block
  • From: Valdis.Kletnieks@xxxxxx
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Paul Davies C <pauldaviesc@xxxxxxxxx>
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Valdis.Kletnieks@xxxxxx
• Re: how do i read a block
  • From: shampavman <shampavman.cg@xxxxxxxxx>
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: 12 <sergio.g.delreal@xxxxxxxxx>
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Valdis.Kletnieks@xxxxxx
• Re: user space device drivers
  • From: Sannu K <sannumail4foss@xxxxxxxxx>
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Paul Davies C <pauldaviesc@xxxxxxxxx>
• Re: user space device drivers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: user space device drivers
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Arun KS <getarunks@xxxxxxxxx>
• Re: user space device drivers
  • From: Gergely Buday <gbuday@xxxxxxxxx>
• Re: user space device drivers
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: user space device drivers
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• Wake on Lan and pci_enable_wake()
  • From: Andy Johnson <johnsonzjo@xxxxxxxxx>
• Re: user space device drivers
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• Re: user space device drivers
  • From: Pietro Paolini <pulsarpietro@xxxxxxx>
• Re: bio size is always 4096
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• PCIe MSI smp_affinity for ARM architecture
  • From: Amit Mahadik <amitmahadik35@xxxxxxxxx>
• PCIe MSI smp_affinity for ARM architecture
  • From: Amit Mahadik <amitmahadik35@xxxxxxxxx>
• Re: user space device drivers
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: how do i read a block
  • From: Prashant Shah <pshah.mumbai@xxxxxxxxx>
• how to debug oom killer errors
  • From: Prashant Shah <pshah.mumbai@xxxxxxxxx>
• Re: user space device drivers
  • From: Gergely Buday <gbuday@xxxxxxxxx>
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Sergio Andrés Gómez del Real <sergio.g.delreal@xxxxxxxxx>
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Valdis.Kletnieks@xxxxxx
• user space device drivers
  • From: Gergely Buday <gbuday@xxxxxxxxx>
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Sergio Andrés Gómez del Real <sergio.g.delreal@xxxxxxxxx>
• Re: how do i read a block
  • From: Matthias Brugger <matthias.bgg@xxxxxxxxx>
• bio size is always 4096
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: how do i read a block
  • From: Valdis.Kletnieks@xxxxxx
• Re: Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: Initial git repository - kernel tree
  • From: Matthias Kaehlcke <matthias.list@xxxxxxxxxxxx>
• Re: Initial git repository - kernel tree
  • From: Alexandru Juncu <alexj@xxxxxxxxxx>
• how do i read a block
  • From: shampavman <shampavman.cg@xxxxxxxxx>
• Re: Initial git repository - kernel tree
  • From: Daniel Baluta <daniel.baluta@xxxxxxxxx>
• Initial git repository - kernel tree
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Mapping of ZONE_HIGHMEM in kernel address space in 32bit x86
  • From: Paul Davies C <pauldaviesc@xxxxxxxxx>
• Re: Processor Comparison
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Processor Comparison
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Processor Comparison
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: unable to set smp_affinity of PCIe interrupt
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Kernel routine to "lock" all of the pages of a particular VMA.
  • From: Valdis.Kletnieks@xxxxxx
• Kernel routine to "lock" all of the pages of a particular VMA.
  • From: Buland Kumar Singh <6b65726e656c@xxxxxxxxx>
• Re: what's the meaning of "%%fs" ?
  • From: Ender Dai <ender.dai@xxxxxxxxx>
• what are gflags of net_device for?
  • From: Andy Johnson <johnsonzjo@xxxxxxxxx>
• Re: cfs scheduler vruntime overflow
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• cfs scheduler vruntime overflow
  • From: 이승훈 <waydi1@xxxxxxxxx>
• Re: Couple of questions on OOM trace.
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• what's the meaning of "%%fs" ?
  • From: lx <lxlenovostar@xxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Couple of questions on OOM trace.
  • From: Shraddha Kamat <sh2008ka@xxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: current tty
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• unable to set smp_affinity of PCIe interrupt
  • From: Amit Mahadik <amitmahadik35@xxxxxxxxx>
• Re: current tty
  • From: Hatte John <june.tune.sea@xxxxxxxxx>
• Analyzing Kernel call traces.
  • From: Shraddha Kamat <sh2008ka@xxxxxxxxx>
• RE: read PCI memory and config spyce through /dev/mem
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• Re: Building multi-file modules
  • From: Yuva Raj <yuvaeasy@xxxxxxxxx>
• current tty
  • From: Hatte John <june.tune.sea@xxxxxxxxx>
• Re: read PCI memory and config spyce through /dev/mem
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• RE: read PCI memory and config spyce through /dev/mem
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• Re: Major number for multipath block devices
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Major number for multipath block devices
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: Gaurav Mahajan <gauravmahajan2007@xxxxxxxxx>
• Re: Device mapper api v/s block device driver api
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: Device mapper api v/s block device driver api
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: Device mapper api v/s block device driver api
  • From: Valdis.Kletnieks@xxxxxx
• Device mapper api v/s block device driver api
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: question about vlan driver
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: question about vlan driver
  • From: Bjørn Mork <bjorn@xxxxxxx>
• question about vlan driver
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: read PCI memory and config spyce through /dev/mem
  • From: Valdis.Kletnieks@xxxxxx
• read PCI memory and config spyce through /dev/mem
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• Re: when to remount sysfs ?
  • From: Karel Zak <kzak@xxxxxxxxxx>
• Re: Kernel panic when using initramfs instead of initrd
  • From: Max Filippov <jcmvbkbc@xxxxxxxxx>
• when to remount sysfs ?
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Kernel panic when using initramfs instead of initrd
  • From: Ivan Nikolaev <voidexp@xxxxxxxxx>
• Circular DMA buffers and userspace vma(s)
  • From: Ilyes Gouta <ilyes.gouta@xxxxxxxxx>
• generating the in-kernel "kerneldoc" guides
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: kernel panic in sample block device driver
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re:Why kernel reloads these segment registers, such as ds, es, .etc in startup_32 ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Why kernel reloads these segment registers, such as ds, es, .etc in startup_32 ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Re: kernel panic in sample block device driver
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: hello and wiki edit
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• Re: Need a good document that explains how to analyze kernel crash dump.
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• Re: Need a good document that explains how to analyze kernel crash dump.
  • From: Prasad Lakshman <prasad.bl.emb@xxxxxxxxx>
• Fwd: Need a good document that explains how to analyze kernel crash dump.
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• searchability of kernelnewbies mailing list archive.
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Need a good document that explains how to analyze kernel crash dump.
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• Need a good document that explains how to analyze kernel crash dump.
  • From: Prasad Lakshman <prasad.bl.emb@xxxxxxxxx>
• Re: kernel panic in sample block device driver
  • From: anish singh <anish198519851985@xxxxxxxxx>
• kernel panic in sample block device driver
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: hello and wiki edit
  • From: Sven Dowideit <SvenDowideit@xxxxxxxxxxx>
• Re: hello and wiki edit
  • From: Sven Dowideit <SvenDowideit@xxxxxxxxxxx>
• updated hands-on tutorial on how to load external firmware from your module
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: hello and wiki edit
  • From: Valdis.Kletnieks@xxxxxx
• Re: hello and wiki edit
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• hello and wiki edit
  • From: Sven Dowideit <SvenDowideit@xxxxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: Gaurav Mahajan <gauravmahajan2007@xxxxxxxxx>
• [help] USB - kernel 3.8 : ULPI timeout
  • From: "Mylene Josserand" <Mylene.Josserand@xxxxxxxxxxx>
• [OT]kernel internship for women
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: Anatol Pomozov <anatol.pomozov@xxxxxxxxx>
• Building multi-file modules
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Documentation on device-mapper and friends
  • From: amit mehta <gmate.amit@xxxxxxxxx>
• Re: Do we use ARM's system mode in linux kernel
  • From: Arun KS <getarunks@xxxxxxxxx>
• still confused by kernel compile msg, "sizeof(struct x86cpu_device_id)=12 ..."
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: oops in a kernel module
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: oops in a kernel module
  • From: Valdis.Kletnieks@xxxxxx
• Re: Documentation on device-mapper and friends
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Documentation on device-mapper and friends
  • From: Kumar Amit Mehta <gmate.amit@xxxxxxxxx>
• oops in a kernel module
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: Compile multiple modules with a single makefile
  • From: Henrique Rodrigues <henriquesilvar@xxxxxxxxx>
• Re: Compile multiple modules with a single makefile
  • From: Henrique Rodrigues <henriquesilvar@xxxxxxxxx>
• Re: Compile multiple modules with a single makefile
  • From: Valdis.Kletnieks@xxxxxx
• Compile multiple modules with a single makefile
  • From: Henrique Rodrigues <henriquesilvar@xxxxxxxxx>
• Re: Do we use ARM's system mode in linux kernel
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• ucontext in signal handler
  • From: "Warlich, Christof" <christof.warlich@xxxxxxxxxxx>
• Do we use ARM's system mode in linux kernel
  • From: Dhiraj Kumar <dhlinx@xxxxxxxxx>
• Re: [HELP] Documentation on CPU:/sys/devices/system/cpu/cpuX/cache/indexX/shared_cpu_map
  • From: edsionte <edsionte@xxxxxxxxx>
• ［OT] How to use relative path in gdb macro
  • From: hz hanks <hankshz@xxxxxxxxx>
• Re: Dynamic Sysfs Attribute Files
  • From: Matt Davis <mattdavis9@xxxxxxxxx>
• anyone else getting "sizeof(struct x86cpu_device_id)" errors compiling kernel?
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• [HELP] cpuidle in SYSFS: /sys/devices/system/cpu/cpu0/cpuidle/state0/desc
  • From: Ren Zhen <darwin.xupt@xxxxxxxxx>
• [HELP]CPU in SYSFS:/sys/devices/system/cpu/cpu0/microcode
  • From: Ren Zhen <darwin.xupt@xxxxxxxxx>
• Re: Dynamic Sysfs Attribute Files
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: Dynamic Sysfs Attribute Files
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• access to hardware registers using KGDB on ARM
  • From: Андрей Скворцов <skvortsov.av@xxxxxxxxxxxxxxxxxx>
• Dynamic Sysfs Attribute Files
  • From: Matt Davis <mattdavis9@xxxxxxxxx>
• Re: Building kernel modules with debuginfo and printing line numbers in kernel oops message / coredump
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: [rrd-users] Can small writes generate a lot of faults?
  • From: Daniel Hilst Selli <danielhilst@xxxxxxxxx>
• Re: Can small writes generate a lot of faults?
  • From: Daniel Hilst Selli <danielhilst@xxxxxxxxx>
• [HELP] Documentation on CPU:/sys/devices/system/cpu/cpuX/cache/indexX/shared_cpu_map
  • From: Ren Zhen <darwin.xupt@xxxxxxxxx>
• Re: Writing device drivers in Linux: A brief tutorial
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• what will kernel_execve() does..?
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: Writing device drivers in Linux: A brief tutorial
  • From: shampavman <shampavman.cg@xxxxxxxxx>
• Re: [HELP] Document: /sys/devices/system/cpu/cpu0/cache/index0/coherency_line_size
  • From: Silviu Popescu <silviupopescu1990@xxxxxxxxx>
• Re: Writing device drivers in Linux: A brief tutorial
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• [HELP] Document: /sys/devices/system/cpu/cpu0/cache/index0/coherency_line_size
  • From: Ren Zhen <darwin.xupt@xxxxxxxxx>
• Re: I2C: kernel & userspace drivers : using i2c-stub
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: I2C: kernel & userspace drivers : using i2c-stub
  • From: Sagar Padhye <sgr.m.pdy@xxxxxxxxx>
• process context value
  • From: Shraddha Kamat <sh2008ka@xxxxxxxxx>
• Re: Can small writes generate a lot of faults?
  • From: Gaurav Jain <gjainroorkee@xxxxxxxxx>
• Re: I2C: kernel & userspace drivers : using i2c-stub
  • From: anish singh <anish198519851985@xxxxxxxxx>
• Writing device drivers in Linux: A brief tutorial
  • From: Zack <zackscary@xxxxxxxxx>
• Re: Can small writes generate a lot of faults?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Fwd: [RFC]CPU in SYSFS: what information should be written to /sys/devices/system/cpu/probe to add cpu In X86?
  • From: Ren Zhen <darwin.xupt@xxxxxxxxx>
• I2C: kernel & userspace drivers : using i2c-stub
  • From: Sagar Padhye <sgr.m.pdy@xxxxxxxxx>
• Re: Something about Redhat
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Fwd: Building kernel modules with debuginfo and printing line numbers in kernel oops message / coredump
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Alternative for API system() in multi-threaded app
  • From: Praveen kumar <chatpravi@xxxxxxxxx>
• Re: Can small writes generate a lot of faults?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Something about Redhat
  • From: Grzegorz Dwornicki <gd1100@xxxxxxxxx>
• Re: Something about Redhat
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: Something about Redhat
  • From: Grzegorz Dwornicki <gd1100@xxxxxxxxx>
• Something about Redhat
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: Building kernel modules with debuginfo and printing line numbers in kernel oops message / coredump
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: Building kernel modules with debuginfo and printing line numbers in kernel oops message / coredump
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: YAFFS2 not part of Linux Kernel
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• Re: Building kernel modules with debuginfo and printing line numbers in kernel oops message / coredump
  • From: Valdis.Kletnieks@xxxxxx
• Re: Check live Virtual Address to Physical Address mappings
  • From: Josh Cartwright <joshc@xxxxxxxxxxxx>
• Re: Building kernel modules with debuginfo and printing line numbers in kernel oops message / coredump
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Can small writes generate a lot of faults?
  • From: Daniel Hilst Selli <danielhilst@xxxxxxxxx>
• Building kernel modules with debuginfo and printing line numbers in kernel oops message / coredump
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: Why the niceness is not always taken into account ?
  • From: Alexandre Laurent <alexandre.laurent@xxxxxxx>
• Re: Check live Virtual Address to Physical Address mappings
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: help needed to do mmap
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Check live Virtual Address to Physical Address mappings
  • From: Shraddha Kamat <sh2008ka@xxxxxxxxx>
• Re: help needed to do mmap
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: help needed to do mmap
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• help needed to do mmap
  • From: er krishna <erkrishna@xxxxxxxxx>
• Re: [ARM-LINUX]Init process is not getting launched while bringing up an opensource kernel on Qualcomm board...
  • From: Sarbojit Ganguly <unixman.linuxboy@xxxxxxxxx>
• Re: [ARM-LINUX]Init process is not getting launched while bringing up an opensource kernel on Qualcomm board...
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: [ARM-LINUX]Init process is not getting launched while bringing up an opensource kernel on Qualcomm board...
  • From: Sarbojit Ganguly <unixman.linuxboy@xxxxxxxxx>
• [ARM-LINUX]Init process is not getting launched while bringing up an opensource kernel on Qualcomm board...
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: Why the niceness is not always taken into account ?
  • From: Valdis.Kletnieks@xxxxxx
• linux-3.8.7 64bit build
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: Why the niceness is not always taken into account ?
  • From: Alexandre Laurent <alexandre.laurent@xxxxxxx>
• Re: Build error in linux-3.8.7
  • From: Sarbojit Ganguly <unixman.linuxboy@xxxxxxxxx>
• Re: Why the niceness is not always taken into account ?
  • From: Valdis.Kletnieks@xxxxxx
• RE: linux-3.8.7 64bit build
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: Why the niceness is not always taken into account ?
  • From: Alexandre Laurent <alexandre.laurent@xxxxxxx>
• Re: scheduler context
  • From: Arun KS <getarunks@xxxxxxxxx>
• scheduler context
  • From: ratheesh kannoth <ratheesh.ksz@xxxxxxxxx>
• Re: net_device: limit rate ot tx packets
  • From: christian+kn@xxxxxxx
• Re: Build error in linux-3.8.7
  • From: Sarbojit Ganguly <unixman.linuxboy@xxxxxxxxx>
• Handling MSI interrupts
  • From: Matti Vaittinen <mazziesaccount@xxxxxxxxx>
• RE: Build error in linux-3.8.7
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• How to debug kernel on ARM with gdb
  • From: Woody Wu <narkewoody@xxxxxxxxx>
• RE: Build error in linux-3.8.7
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• RE: Build error in linux-3.8.7
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: Build error in linux-3.8.7
  • From: Sarbojit Ganguly <unixman.linuxboy@xxxxxxxxx>
• RE: Build error in linux-3.8.7
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: Build error in linux-3.8.7
  • From: Sarbojit Ganguly <unixman.linuxboy@xxxxxxxxx>
• Re: Invitation to connect on LinkedIn
  • From: Leon Romanovsky <leon@xxxxxxx>
• Build error in linux-3.8.7
  • From: "Giridhara RP (grp)" <grp@xxxxxxxxx>
• Re: So I want to get some kernel routine called....
  • From: Valdis.Kletnieks@xxxxxx
• Re: YAFFS2 not part of Linux Kernel
  • From: Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx>
• So I want to get some kernel routine called....
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Module needs to lookup its own symbols at runtime.
  • From: "devendra.aaru" <devendra.aaru@xxxxxxxxx>
• Module needs to lookup its own symbols at runtime.
  • From: Neil Baylis <neil.baylis@xxxxxxxxx>
• Re: Why the niceness is not always taken into account ?
  • From: Kristof Provost <kristof@xxxxxxxxxx>
• Re: YAFFS2 not part of Linux Kernel
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Why the niceness is not always taken into account ?
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: Why the niceness is not always taken into account ?
  • From: Alexandre Laurent <alexandre.laurent@xxxxxxx>
• YAFFS2 not part of Linux Kernel
  • From: Pietro Paolini <pulsarpietro@xxxxxxx>
• Re: SNORT/SURICATA LEARNing
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: SNORT/SURICATA LEARNing
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• SNORT/SURICATA LEARNing
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: Why the niceness is not always taken into account ?
  • From: Kristof Provost <kristof@xxxxxxxxxx>
• Why the niceness is not always taken into account ?
  • From: Alexandre Laurent <alexandre.laurent@xxxxxxx>
• Re: File System Learning Approach
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: File System Learning Approach
  • From: Pietro Paolini <pulsarpietro@xxxxxxx>
• Re: File System Learning Approach
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Where is /dev/mtdX on Linux-3.8.0-rc7+
  • From: Yuva Raj <yuvaeasy@xxxxxxxxx>
• Re: File System Learning Approach
  • From: Valdis.Kletnieks@xxxxxx
• File System Learning Approach
  • From: Pietro Paolini <pulsarpietro@xxxxxxx>
• who calls tx callback of the networking device
  • From: "devendra.aaru" <devendra.aaru@xxxxxxxxx>
• Re: simple question about struct pointer
  • From: arshad hussain <arshad.super@xxxxxxxxx>
• Where is /dev/mtdX on Linux-3.8.0-rc7+
  • From: bill4carson <bill4carson@xxxxxxxxx>
• simple question about struct pointer
  • From: Ben Wu <crayben@xxxxxxxx>
• Re: net_device: limit rate ot tx packets
  • From: Valdis.Kletnieks@xxxxxx
• Re: net_device: limit rate ot tx packets
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: net_device: limit rate ot tx packets
  • From: Valdis.Kletnieks@xxxxxx
• Re: net_device: limit rate ot tx packets
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• net_device: limit rate ot tx packets
  • From: christian+kn@xxxxxxx
• Re: Forum for asking questions related to block device drivers
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: Forum for asking questions related to block device drivers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Forum for asking questions related to block device drivers
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Forum for asking questions related to block device drivers
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: Forum for asking questions related to block device drivers
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: Forum for asking questions related to block device drivers
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: Forum for asking questions related to block device drivers
  • From: Rajat Sharma <fs.rajat@xxxxxxxxx>
• Re: How will Linux community support the coming Intel new chip Bay Trail?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Re: How will Linux community support the coming Intel new chip Bay Trail?
  • From: Valdis.Kletnieks@xxxxxx
• Re: Forum for asking questions related to block device drivers
  • From: neha naik <nehanaik27@xxxxxxxxx>
• How will Linux community support the coming Intel new chip Bay Trail?
  • From: Peter Xu <xzpeter@xxxxxxxxx>
• Re: Forum for asking questions related to block device drivers
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: Linux from scratch
  • From: Alexandru Juncu <alexj@xxxxxxxxxx>
• Re: Linux from scratch
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Forum for asking questions related to block device drivers
  • From: Rajat Sharma <fs.rajat@xxxxxxxxx>
• Forum for asking questions related to block device drivers
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Kexec sys call code
  • From: leo kirotawa <kirotawa@xxxxxxxxx>
• Re: the github repo, and bugzilla.kernel.org
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• the github repo, and bugzilla.kernel.org
  • From: Haix64 <hossein.aix64@xxxxxxxxx>
• Re: open_softirq do?
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• open_softirq do?
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: At which Network Layer
  • From: Yi Li <lovelylich@xxxxxxxxx>
• At which Network Layer
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: Linux from scratch
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Passthrough device driver performance is low on reads compared to writes
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: Building multiple .ko files from a single module
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: Building multiple .ko files from a single module
  • From: Kristof Provost <kristof@xxxxxxxxxx>
• Re: Building multiple .ko files from a single module
  • From: Moritz Fischer <moritz.fischer@xxxxxxxxx>
• Re: Linux from scratch
  • From: Alexandru Juncu <alexj@xxxxxxxxxx>
• Re: Linux from scratch
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Linux from scratch
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Building multiple .ko files from a single module
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: Linux from scratch
  • From: Silviu Popescu <silviupopescu1990@xxxxxxxxx>
• Linux from scratch
  • From: Alexandru Juncu <alexj@xxxxxxxxxx>
• Re: Kernel generates vmImage instead of zImage
  • From: Onur Cem Çelebi <occelebi@xxxxxxxxx>
• Re: Interrupt Handler of Ethernet Device
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: Interrupt Handler of Ethernet Device
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: simple question about the function memcmp in kernel
  • From: Burke <crayben@xxxxxxxx>
• Re: simple question about the function memcmp in kernel
  • From: Valdis.Kletnieks@xxxxxx
• Re: simple question about the function memcmp in kernel
  • From: Max Filippov <jcmvbkbc@xxxxxxxxx>
• Re: simple question about the function memcmp in kernel
  • From: Valdis.Kletnieks@xxxxxx
• simple question about the function memcmp in kernel
  • From: Ben Wu <crayben@xxxxxxxx>
• Re: Interrupt Handler of Ethernet Device
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: Interrupt Handler of Ethernet Device
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: Using vmalloc in device driver code
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: Interrupt Handler of Ethernet Device
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Interrupt Handler of Ethernet Device
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: Interrupt Handler of Ethernet Device
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Interrupt Handler of Ethernet Device
  • From: Robert Clove <cloverobert@xxxxxxxxx>
• Re: Using vmalloc in device driver code
  • From: Arun KS <getarunks@xxxxxxxxx>
• Re: Using vmalloc in device driver code
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: NMIs, Locks, linked lists, barriers, and rculists, oh my!
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: NMIs, Locks, linked lists, barriers, and rculists, oh my!
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Using vmalloc in device driver code
  • From: neha naik <nehanaik27@xxxxxxxxx>
• Re: Can anyone plz explain me the fields
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: NMIs, Locks, linked lists, barriers, and rculists, oh my!
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: Related to Network packet in kernel
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: Kernel generates vmImage instead of zImage
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Kernel generates vmImage instead of zImage
  • From: Augusto Mecking Caringi <augustocaringi@xxxxxxxxx>
• Can anyone plz explain me the fields
  • From: Tarun Batra <tbatra18@xxxxxxxxx>
• Related to Network packet in kernel
  • From: Tarun Batra <tbatra18@xxxxxxxxx>
• socket MSG_DONTROUTE option on local sockets
  • From: "devendra.aaru" <devendra.aaru@xxxxxxxxx>
• Re: Kernel generates vmImage instead of zImage
  • From: Onur Cem Çelebi <occelebi@xxxxxxxxx>
• Re: Kernel generates vmImage instead of zImage
  • From: Christophe Aeschlimann <c.aeschlimann@xxxxxxxxxxxx>
• Re: Kernel generates vmImage instead of zImage
  • From: Onur Cem Çelebi <occelebi@xxxxxxxxx>
• Re: Kernel generates vmImage instead of zImage
  • From: Onur Cem Çelebi <occelebi@xxxxxxxxx>
• Re: NMIs, Locks, linked lists, barriers, and rculists, oh my!
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: A few questions about the kernel-janitors project.
  • From: Jerry Zhang <jerry.scofield@xxxxxxxxx>
• A few questions about the kernel-janitors project.
  • From: Jerry Zhang <jerry.scofield@xxxxxxxxx>
• Re: NMIs, Locks, linked lists, barriers, and rculists, oh my!
  • From: Valdis.Kletnieks@xxxxxx
• Re: Kernel generates vmImage instead of zImage
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• NMIs, Locks, linked lists, barriers, and rculists, oh my!
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: [help] kernel oops in function gpio_to_irq
  • From: "Mylene Josserand" <Mylene.Josserand@xxxxxxxxxxx>
• Re: Method to calculate user space thread size
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: Method to calculate user space thread size
  • From: Valdis.Kletnieks@xxxxxx
• block level cow operation
  • From: Prashant Shah <pshah.mumbai@xxxxxxxxx>
• Kernel generates vmImage instead of zImage
  • From: Onur Cem Çelebi <occelebi@xxxxxxxxx>
• sample network driver
  • From: Tarun Batra <tbatra18@xxxxxxxxx>
• Re: Method to calculate user space thread size
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• Re: Method to calculate user space thread size
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: Method to calculate user space thread size
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: cgroup.procs versus tasks (cgroups)
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: Reading linux boot args
  • From: manty kuma <mantykuma@xxxxxxxxx>
• Re: Online migration of arbitrary filesystems, possible?
  • From: Valdis.Kletnieks@xxxxxx
• Re: cgroup.procs versus tasks (cgroups)
  • From: Valdis.Kletnieks@xxxxxx
• Re: Reading linux boot args
  • From: Valdis.Kletnieks@xxxxxx
• Re: cgroup.procs versus tasks (cgroups)
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: kernel build error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Method to calculate user space thread size
  • From: naveen yadav <yad.naveen@xxxxxxxxx>
• Re: [help] kernel oops in function gpio_to_irq
  • From: "Mylene Josserand" <Mylene.Josserand@xxxxxxxxxxx>
• What is idr_alloc()
  • From: Manavendra Nath Manav <mnm.kernel@xxxxxxxxx>
• Re: cgroup.procs versus tasks (cgroups)
  • From: Vlad Dogaru <ddvlad@xxxxxxxxxxxxxxxx>
• Re: kernel build error
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• [ARM-LINUX]Booting is stopped at "CPSIE" instruction
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Reading linux boot args
  • From: manty kuma <mantykuma@xxxxxxxxx>
• Re: kernel build error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• cgroup.procs versus tasks (cgroups)
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: what does it use two "!!"
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: Online migration of arbitrary filesystems, possible?
  • From: Jason Ball <jason@xxxxxxxx>
• Re: Online migration of arbitrary filesystems, possible?
  • From: Daniel Hilst <danielhilst@xxxxxxxxx>
• Re: Online migration of arbitrary filesystems, possible?
  • From: Daniel Hilst <danielhilst@xxxxxxxxx>
• Re: what does it use two "!!"
  • From: Christopher Harvey <chris@xxxxxxxxxxxxxxxx>
• Re: what does it use two "!!"
  • From: Valdis.Kletnieks@xxxxxx
• Re: pci_alloc_consistent doubt
  • From: Dhananjay Maske <dhananjay.maske87@xxxxxxxxx>
• what does it use two "!!"
  • From: Ben Wu <crayben@xxxxxxxx>
• Re: what does it use two "!!"
  • From: anish singh <anish198519851985@xxxxxxxxx>
• what does it use two "!!"
  • From: Ben Wu <crayben@xxxxxxxx>
• Re: pci_alloc_consistent doubt
  • From: Avinash Patil <avinashapatil@xxxxxxxxx>
• Re: Signal handlers
  • From: Yousef Alhashemi <yousef.alhashemi@xxxxxxxxx>
• Signal handlers
  • From: Rahul Gandhi <rahul.rahulgags@xxxxxxxxx>
• Re: pci_alloc_consistent doubt
  • From: Dhananjay Maske <dhananjay.maske87@xxxxxxxxx>
• Re: extended asm and register clobbers
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Paulo Petruzalek <ppetruzalek@xxxxxxxxxxxx>
• Re: pci_alloc_consistent doubt
  • From: Dhananjay Maske <dhananjay.maske87@xxxxxxxxx>
• Re: How is gpio_keys.ko supposed to work?
  • From: Sven Geggus <lists@xxxxxxxxxxxxxxxxxxxxx>
• Re: why not choose another way to define the _IOC_xxxMASK related to the ioctl
  • From: Valdis.Kletnieks@xxxxxx
• Re: [help] kernel oops in function gpio_to_irq
  • From: Matthias Brugger <matthias.bgg@xxxxxxxxx>
• Re:Re: why not choose another way to define the _IOC_xxxMASK related to the ioctl
  • From: RS <tinyshrimp@xxxxxxx>
• Re: why not choose another way to define the _IOC_xxxMASK related to the ioctl
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• why not choose another way to define the _IOC_xxxMASK related to the ioctl
  • From: RS <tinyshrimp@xxxxxxx>
• Re: Online migration of arbitrary filesystems, possible?
  • From: Valdis.Kletnieks@xxxxxx
• Re: Online migration of arbitrary filesystems, possible?
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• Online migration of arbitrary filesystems, possible?
  • From: Daniel Hilst <danielhilst@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: How is gpio_keys.ko supposed to work?
  • From: Jerry Zhang <jerry.scofield@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Manish Katiyar <mkatiyar@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Madper <bbboson@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Valdis.Kletnieks@xxxxxx
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Fwd: Creating mkfs for my custom filesystem
  • From: Pranay Srivastava <pranjas@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• Re: Creating mkfs for my custom filesystem
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re:Re: elf_map: why offset of vma need to subtract eppnt->p_vaddr ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Re: Re: elf_map: why offset of vma need to subtract eppnt->p_vaddr ?
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: elf_map: why offset of vma need to subtract eppnt->p_vaddr ?
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Creating mkfs for my custom filesystem
  • From: Sankar P <sankar.curiosity@xxxxxxxxx>
• elf_map: why offset of vma need to subtract eppnt->p_vaddr ?
  • From: Jacky <jackyclivia@xxxxxxx>
• How is gpio_keys.ko supposed to work?
  • From: Sven Geggus <lists@xxxxxxxxxxxxxxxxxxxxx>
• Re: pci_alloc_consistent doubt
  • From: Dhananjay Maske <dhananjay.maske87@xxxxxxxxx>
• pci_alloc_consistent doubt
  • From: Dhananjay Maske <dhananjay.maske87@xxxxxxxxx>
• Re: initramfs_list
  • From: Valdis.Kletnieks@xxxxxx
• [help] kernel oops in function gpio_to_irq
  • From: "Mylene Josserand" <Mylene.Josserand@xxxxxxxxxxx>
• initramfs_list
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: Driver managing network interface
  • From: Kristof Provost <kristof@xxxxxxxxxx>
• Driver managing network interface
  • From: Pietro Paolini <pulsarpietro@xxxxxxx>
• Re: SSDs vs elevators (was Re: cap on writeback?)
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• feature removal schedule is removed ?
  • From: David Shwatrz <dshwatrz@xxxxxxxxx>
• Re: feature removal schedule is removed ?
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: feature removal schedule is removed ?
  • From: Jonathan Neuschäfer <j.neuschaefer@xxxxxxx>
• Re: question about
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Matthias Brugger <matthias.bgg@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• cap on writeback?
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: cap on writeback?
  • From: Valdis.Kletnieks@xxxxxx
• Re: cap on writeback?
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: cap on writeback?
  • From: Valdis.Kletnieks@xxxxxx
• Re: cap on writeback?
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• what does the kernel does after it is being notified of incoming Frame
  • From: Tarun Batra <tbatra18@xxxxxxxxx>
• SSDs vs elevators (was Re: cap on writeback?)
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: what does the kernel does after it is being notified of incoming Frame
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• relationship between cpu_affinity and Packet RX Processing
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: relationship between cpu_affinity and Packet RX Processing
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: kernel build error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Why we Use both mm_users and mm_count in struct mm_struct{ }
  • From: anish singh <anish198519851985@xxxxxxxxx>
• Re: Why we Use both mm_users and mm_count in struct mm_struct{ }
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: Why we Use both mm_users and mm_count in struct mm_struct{ }
  • From: Niroj Pokhrel <nirojpokhrel@xxxxxxxxx>
• Re: Why we Use both mm_users and mm_count in struct mm_struct{ }
  • From: anish singh <anish198519851985@xxxxxxxxx>
• Re: kernel build error
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: initramfs.cpio
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: question about
  • From: Moritz Fischer <moritz.fischer@xxxxxxxxx>
• question about
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: Why we Use both mm_users and mm_count in struct mm_struct{ }
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: initramfs.cpio
  • From: Valdis.Kletnieks@xxxxxx
• initramfs.cpio
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: kernel build error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: optimization in kernel compile
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Matthias Brugger <matthias.bgg@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Matthias Brugger <matthias.bgg@xxxxxxxxx>
• time: Questions about kernel function timekeeping_bigadjust()
  • From: Dong ZHu <bluezhudong@xxxxxxxxx>
• Why we Use both mm_users and mm_count in struct mm_struct{ }
  • From: Niroj Pokhrel <nirojpokhrel@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Valdis.Kletnieks@xxxxxx
• Re: optimization in kernel compile
  • From: Valdis.Kletnieks@xxxxxx
• Re: optimization in kernel compile
  • From: Valdis.Kletnieks@xxxxxx
• Re: optimization in kernel compile
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: optimization in kernel compile
  • From: Valdis.Kletnieks@xxxxxx
• Confusion in the usage of linux key management APIs
  • From: Ranjan Sinha <rnjn.sinha@xxxxxxxxx>
• [Need Help] time: questions about kernel function timekeeping_bigadjust()
  • From: Dong Zhu <bluezhudong@xxxxxxxxx>
• Re: kernel build error
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• optimization in kernel compile
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel build error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Userspace access to PCIe - SATA device memory BAR
  • From: John Beard <john.j.beard@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Valdis.Kletnieks@xxxxxx
• Re: kernel build error
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: wake_lock in linux kernel
  • From: Yuva Raj <yuvaeasy@xxxxxxxxx>
• Re: Linux elevators (Re: BFQ: simple elevator)
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: Linux elevators (Re: BFQ: simple elevator)
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Linux elevators (Re: BFQ: simple elevator)
  • From: Valdis.Kletnieks@xxxxxx
• Re: BFQ: simple elevator
  • From: Valdis.Kletnieks@xxxxxx
• Linux elevators (Re: BFQ: simple elevator)
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• DMA attributes with dma_sync_single()
  • From: Moritz Fischer <moritz.fischer@xxxxxxxxx>
• Re: BFQ: simple elevator
  • From: Valdis.Kletnieks@xxxxxx
• Re: BFQ: simple elevator
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Memory allocations in linux for processes
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel build error
  • From: Valdis.Kletnieks@xxxxxx
• BFQ: simple elevator
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• About time delay in kernel threads at LOCAL_OUT netfilter hook
  • From: Rifat Rahman <rifatrahmanovi@xxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
• wake_lock in linux kernel
  • From: Ben Wu <crayben@xxxxxxxx>
• Re: kernel build error
  • From: Ben Wu <crayben@xxxxxxxx>
• Wake_lock in linux kernel
  • From: "Ben Wu" <2110150311@xxxxxxxxxxxxxxxx>
• Re: kernel build error
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: kernel build error
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: do_initcalls
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: Victor Buciuc <victor.buciuc@xxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: Alec Joseph Rivera <eijhei@xxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: Memory allocations in linux for processes
  • From: Valdis.Kletnieks@xxxxxx
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: Dave Hylands <dhylands@xxxxxxxxx>
• Re: Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Design Patterns in Linux Kernel: Fancy Tricks With Linked Lists
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: Memory allocations in linux for processes
  • From: Niroj Pokhrel <nirojpokhrel@xxxxxxxxx>
• Re: Memory allocations in linux for processes
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel build error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Kernel warning messages- protocol 0000 is buggy, dev eth0
  • From: Bjørn Mork <bjorn@xxxxxxx>
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: Haix64 <hossein.aix64@xxxxxxxxx>
• Kernel warning messages- protocol 0000 is buggy, dev eth0
  • From: Sengottuvelan S <sengottuvelan.s@xxxxxxxxx>
• Re: kernel build error
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: programme header
  • From: Valdis.Kletnieks@xxxxxx
• Re: programme header
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: programme header
  • From: Valdis.Kletnieks@xxxxxx
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: "Leonid V. Fedorenchik" <leonidsbox@xxxxxxxxx>
• Re: programme header
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: do_initcalls
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: do_initcalls
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: signals handling: kill() successful, but nothing delivered
  • From: Valdis.Kletnieks@xxxxxx
• Re: creat all the dentry objects in memory when mount a fs?
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: Alexandre Borges <alex_sun@xxxxxxxxxxxx>
• Memory allocations in linux for processes
  • From: Niroj Pokhrel <nirojpokhrel@xxxxxxxxx>
• A question on the vale of memory water marks
  • From: larmbr zhan <nasa4836@xxxxxxxxx>
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: rakesh Bhaskar <everfriendlyrakesh@xxxxxxxxx>
• creat all the dentry objects in memory when mount a fs?‏
  • From: RS <tinyshrimp@xxxxxxx>
• Re: signals handling: kill() successful, but nothing delivered
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: Rohan Puri <rohan.puri15@xxxxxxxxx>
• Re: hpet misc device usage
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: kernel build error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: Arlie Stephens <arlie@xxxxxxxxxxxx>
• Re: do_initcalls
  • From: ishare <june.tune.sea@xxxxxxxxx>
• kernel build error
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Re: do_initcalls
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: Tobias Boege <tobias@xxxxxxxxxxxxxx>
• do_initcalls
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: for interested folks, i'll announce new kernel tutorials via twitter
  • From: NeonJohn <jgd@xxxxxxxxxxxxx>
• for interested folks, i'll announce new kernel tutorials via twitter
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: kmem_cache_init
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• hpet misc device usage
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: now in progress -- tutorial on udev
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: now in progress -- tutorial on udev
  • From: Haix64 <hossein.aix64@xxxxxxxxx>
• now in progress -- tutorial on udev
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• numerous kernel tutorials coming shortly
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: linux-newbie vs kernelnewbies
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: linux-newbie vs kernelnewbies
  • From: Jack Wang <xjtuwjp@xxxxxxxxx>
• linux-newbie vs kernelnewbies
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: block mailing list?
  • From: Valdis.Kletnieks@xxxxxx
• block mailing list?
  • From: Raymond Jennings <shentino@xxxxxxxxx>
• Re: kmem_cache_init
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: Need of different memory zones
  • From: Arun KS <getarunks@xxxxxxxxx>
• Re: Need of different memory zones
  • From: Niroj Pokhrel <nirojpokhrel@xxxxxxxxx>
• [ARM-LINUX] Quiry regarding the DMA mapping.
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: networking question
  • From: "devendra.aaru" <devendra.aaru@xxxxxxxxx>
• Re: Need of different memory zones
  • From: Arun KS <getarunks@xxxxxxxxx>
• Re: kmem_cache_init
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• kmem_cache_init
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: networking question
  • From: Rami Rosen <roszenrami@xxxxxxxxx>
• Re: Need of different memory zones
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• When to use blk_end_request_* routines.
  • From: Pranay Kumar Srivastava <Pranay.Shrivastava@xxxxxxx>
• networking question
  • From: "devendra.aaru" <devendra.aaru@xxxxxxxxx>
• Unlocking task_list read lock before performing a sleepy operation
  • From: Pranami Bhattacharya <pranami.bhattacharya@xxxxxxxxx>
• nmi_watchdog kernel parameter is set but NMI interrupts are not incremented
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Implementing Network Packet Capturing in Linux-3.5.7
  • From: Prasad Lakshman <prasad.bl.emb@xxxxxxxxx>
• BUG: unable to handle kernel paging request EIP is at kmem_cache_alloc when testing a new bluetooth driver
  • From: Ahmed Abdelfattah <ahmed.abdelfattah.elshemisy@xxxxxxxxx>
• Re: Need of different memory zones
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Need of different memory zones
  • From: Niroj Pokhrel <nirojpokhrel@xxxxxxxxx>
• Re: pthread_lock
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: User space memory
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: Is this normal or wrong?
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: pthread_lock
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Difference between task_active_pid_ns(current) and current->nsproxy->pid.
  • From: Raphael S Carvalho <raphael.scarv@xxxxxxxxx>
• Re: User space memory
  • From: Valdis.Kletnieks@xxxxxx
• Re: User space memory
  • From: Christoph Seitz <c.seitz@xxxxxxxx>
• Re: User space memory
  • From: Valdis.Kletnieks@xxxxxx
• Re: Is this normal or wrong?
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: User space memory
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: pthread_lock
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Explanation of <asm/gpio.h> in Doc/gpio.txt seems out of date
  • From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx>
• Re: pi_waiters in task_struct
  • From: Yuva Raj <yuvaeasy@xxxxxxxxx>
• pi_waiters in task_struct
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: location of inbuilt system call implementation
  • From: Denis Kirjanov <kirjanov@xxxxxxxxx>
• the most socket num of epoll
  • From: ishare <june.tune.sea@xxxxxxxxx>
• location of inbuilt system call implementation
  • From: Niroj Pokhrel <nirojpokhrel@xxxxxxxxx>
• Re: 64bit MMIO access
  • From: Valdis.Kletnieks@xxxxxx
• Re: 64bit MMIO access
  • From: Valdis.Kletnieks@xxxxxx
• Re: 64bit MMIO access
  • From: Jagath Weerasinghe <jagfoss@xxxxxxxxx>
• User space memory
  • From: Christoph Seitz <c.seitz@xxxxxxxx>
• Re: Userspace interception of locally valid memory location
  • From: Valdis.Kletnieks@xxxxxx
• Re: Userspace interception of locally valid memory location
  • From: Valdis.Kletnieks@xxxxxx
• Userspace interception of locally valid memory location
  • From: harish badrinath <harishbadrinath@xxxxxxxxx>
• Re: Disabling interrupts and masking interrupts
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: TLB shootdowns in /proc/interrupts (different results)
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• help with page_fault
  • From: ishare <june.tune.sea@xxxxxxxxx>
• TLB shootdowns in /proc/interrupts (different results)
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re:Re: Will kernel in-place decompression overwrite uncompressed part ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Re: Will kernel in-place decompression overwrite uncompressed part ?
  • From: leo kirotawa <kirotawa@xxxxxxxxx>
• Will kernel in-place decompression overwrite uncompressed part ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Re:Re: Re: What is the memory region ?
  • From: baisheng_wang <baisheng_wang@xxxxxxx>
• Why FIB_TABLE_HASHSZ=2 when CONFIG_IP_ROUTE_MULTIPATH
  • From: tingwei liu <tingw.liu@xxxxxxxxx>
• Re: Re: What is the memory region ?
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• signals handling: kill() successful, but nothing delivered
  • From: michi1@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
• Re: Disabling interrupts and masking interrupts
  • From: Dave Hylands <dhylands@xxxxxxxxx>
• Re: Disabling interrupts and masking interrupts
  • From: Valdis.Kletnieks@xxxxxx
• Re: Disabling interrupts and masking interrupts
  • From: Dave Hylands <dhylands@xxxxxxxxx>
• Re: Disabling interrupts and masking interrupts
  • From: Valdis.Kletnieks@xxxxxx
• Re: Disabling interrupts and masking interrupts
  • From: anish singh <anish198519851985@xxxxxxxxx>
• Re: Disabling interrupts and masking interrupts
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: Disabling interrupts and masking interrupts
  • From: anish singh <anish198519851985@xxxxxxxxx>
• Is this normal or wrong?
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re:Re: What is the memory region ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Disabling interrupts and masking interrupts
  • From: Kevin Wilson <wkevils@xxxxxxxxx>
• Re: zap_low_mappings
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: What is the memory region ?
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re: Several unrelated beginner questions.
  • From: Prabhakar Lad <prabhakar.csengg@xxxxxxxxx>
• What is the memory region ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Reading the framebuffer area.
  • From: manty kuma <mantykuma@xxxxxxxxx>
• RE:Query on skb buffer (Kumar amit mehta)
  • From: Pranay Kumar Srivastava <Pranay.Shrivastava@xxxxxxx>
• Re: zap_low_mappings
  • From: Valdis.Kletnieks@xxxxxx
• Re: zap_low_mappings
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: zap_low_mappings
  • From: Valdis.Kletnieks@xxxxxx
• Re: zap_low_mappings
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: zap_low_mappings
  • From: Valdis.Kletnieks@xxxxxx
• zap_low_mappings
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: Several unrelated beginner questions.
  • From: Valdis.Kletnieks@xxxxxx
• Re: Several unrelated beginner questions.
  • From: Gaurav Jain <gjainroorkee@xxxxxxxxx>
• Several unrelated beginner questions.
  • From: Konstantin Kowalski <kostya-kow@xxxxxxx>
• Re: Query on skb buffer
  • From: Valdis.Kletnieks@xxxxxx
• Query on skb buffer
  • From: Kumar amit mehta <gmate.amit@xxxxxxxxx>
• Creation Of New Partition in EMMC
  • From: "Ranganath T.M" <ranganathtm88@xxxxxxxxx>
• Re: Regarding GPIO driver module
  • From: Prabhakar Lad <prabhakar.csengg@xxxxxxxxx>
• Regarding GPIO driver module
  • From: Rajesh Bhaskaran <cb.rajesh.in@xxxxxxxxx>
• RE: Major/minor numbers
  • From: Pranay Kumar Srivastava <Pranay.Shrivastava@xxxxxxx>
• RE: Major/minor numbers
  • From: Pranay Kumar Srivastava <Pranay.Shrivastava@xxxxxxx>
• Re: Some Links for Easy Understanding of Linux of Kernel Source code
  • From: Anand Arumugam <anand.arumug@xxxxxxxxx>
• Some Links for Easy Understanding of Linux of Kernel Source code
  • From: praveen kumar <spkr322@xxxxxxxxx>
• Re: Major/minor numbers
  • From: Anuz Pratap Singh Tomar <chambilkethakur@xxxxxxxxx>
• Re: pthread_lock
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: pthread_lock
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• Major/minor numbers
  • From: Shraddha Kamat <sh2008ka@xxxxxxxxx>
• Re: pthread_lock
  • From: Valdis.Kletnieks@xxxxxx
• Re: pthread_lock
  • From: Mandeep Sandhu <mandeepsandhu.chd@xxxxxxxxx>
• pthread_lock
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: Module compilation error
  • From: Valdis.Kletnieks@xxxxxx
• Re: Module compilation error
  • From: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
• Module compilation error
  • From: Pietro Paolini <pulsarpietro@xxxxxxx>
• MTD NOR write issue for files greater than a few hundred bytes
  • From: "Holmes, Michael A (Mike)" <Mike.Holmes@xxxxxxx>
• Re: How to measure the RAM read/write performance
  • From: Arun KS <getarunks@xxxxxxxxx>
• Re: How to get RFC documents?
  • From: Valdis.Kletnieks@xxxxxx
• Re: [ARM_LINUX] ioremap() allowing to map system memory...
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• RE: [ARM_LINUX] ioremap() allowing to map system memory...
  • From: buyitian <buyit@xxxxxxx>
• How to get RFC documents?
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: How to measure the RAM read/write performance
  • From: Arun KS <getarunks@xxxxxxxxx>
• Re: how to trace tcp protocol stack ?
  • From: Valdis.Kletnieks@xxxxxx
• Re: how to trace tcp protocol stack ?
  • From: richard -rw- weinberger <richard.weinberger@xxxxxxxxx>
• how to trace tcp protocol stack ?
  • From: ishare <june.tune.sea@xxxxxxxxx>
• Re: Why vmlinux.bin are changed from raw image to elf for x86 ?
  • From: Valdis.Kletnieks@xxxxxx
• Re: [ARM_LINUX] ioremap() allowing to map system memory...
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: [ARM_LINUX] ioremap() allowing to map system memory...
  • From: Prabhu nath <gprabhunath@xxxxxxxxx>
• Re:Why vmlinux.bin are changed from raw image to elf for x86 ?
  • From: Jacky <jackyclivia@xxxxxxx>
• wby mapping beyond end by "MAPPING_BEYOND_END" ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Doubts about vt tty driver
  • From: Chinmay Bapat <cdbapat92@xxxxxxxxx>
• Why vmlinux.bin are changed from raw image to elf for x86 ?
  • From: Jacky <jackyclivia@xxxxxxx>
• Re: How to measure the RAM read/write performance
  • From: sandeep kumar <coolsandyforyou@xxxxxxxxx>
• Re: [filesystem] struct of m_inode
  • From: Valdis.Kletnieks@xxxxxx