Index of tech-kern for July, 2003


FromSubject
07/01/2003
matthew green re: alternate rough SA patch (works on SMP)
Lennart Augustsson Re: alternate rough SA patch (works on SMP)
matthew green re: Update: rough SA patch (works on SMP)
Peter Bex MTD driver cleanup
Robert Elz Re: MTD driver cleanup
Christian Limpach Re: alternate rough SA patch (works on SMP)
Martin Husemann Re: MTD driver cleanup
joseph@magnesium.net Re: USB CD-Writer shows up as CD-ROM only
Frederick Bruckman Re: USB CD-Writer shows up as CD-ROM only
07/02/2003
Darren Reed Some notes on ktrace lwp changes.
Antti Kantee Re: libpthread
YAMAMOTO Takashi make vnodes freeable
Nathan Langford microkernels
Jonathan Kay terabyte array and negative cylinders
Tom Ivar Helbekkmo Re: microkernels
Ian Zagorskih Re: microkernels
David Laight Re: terabyte array and negative cylinders
Yosep Re: Daemon
Bill Studenmund Re: make vnodes freeable
Frederick Bruckman Re: Daemon
Yosep Re: Daemon
Bill Studenmund Re: Some notes on ktrace lwp changes.
Daniel Brewer fsync performance hit on 1.6.1
Stephan Uphoff Re: Update: rough SA patch (works on SMP)
Manuel Bouyer Re: fsync performance hit on 1.6.1
Ivo Vachkov Re: microkernels
felix zaslavskiy Re: microkernels
Gary Thorpe Re: microkernels
Steve Rumble Re: microkernels
Matthew Mondor Re: microkernels
Bill Studenmund MI changes, was Re: ktrace records now get lwp id
Jonathan Stone FYI: this time, really about to import crypto framework
Bill Studenmund Re: make vnodes freeable
Stephan Uphoff Re: make vnodes freeable
Bill Studenmund Re: make vnodes freeable
07/03/2003
Ian Zagorskih Re: microkernels
YAMAMOTO Takashi Re: make vnodes freeable
Daniel Brewer Re: fsync performance hit on 1.6.1
Ignatios Souvatzis Re: terabyte array and negative cylinders
David Laight Re: terabyte array and negative cylinders
Ian Zagorskih Re: microkernels
Stephen Ma fsync performance hit on 1.6.1
Tom Ivar Helbekkmo Re: Update: rough SA patch (works on SMP)
Greywolf Re: terabyte array and negative cylinders
07/04/2003
Simon Burge Re: make vnodes freeable
matthew green re: make vnodes freeable
enami tsugutomo Re: fsync performance hit on 1.6.1
YAMAMOTO Takashi Re: make vnodes freeable
David Laight SYS___syscall and linux (etc) compatibility
Ben Harris Re: SYS___syscall and linux (etc) compatibility
David Laight Re: SYS___syscall and linux (etc) compatibility
07/05/2003
Alexander Yurchenko Re: Promise Ultra60/100 vs 48-bit LBA compliant drives
07/06/2003
noguchi kernel panic with port-i386 and IEEE1394-SBP2
Matthias Drochner Re: kernel panic with port-i386 and IEEE1394-SBP2
Chuck Silvers Re: fsync performance hit on 1.6.1
Manuel Bouyer Re: USB CD-Writer shows up as CD-ROM only
Joseph Dunn Re: USB CD-Writer shows up as CD-ROM only
07/07/2003
noguchi Re: kernel panic with port-i386 and IEEE1394-SBP2
enami tsugutomo Re: fsync performance hit on 1.6.1
Daniel Brewer Re: fsync performance hit on 1.6.1
der Mouse Re: fsync performance hit on 1.6.1
Sam Thigpen Real Time NetBSD & Assembly [Re: how to detect if kernel is running
Simon Burge Re: Real Time NetBSD & Assembly [Re: how to detect if kernel is running in inte
Takeshi Nakayama Re: Promise Ultra66/100 vs 48-bit LBA compliant drives
Chuck Silvers Re: fsync performance hit on 1.6.1
Chuck Silvers Re: fsync performance hit on 1.6.1
Hubert Feyrer making a netbsd kernel look like a linux kernel? [was: Re: non-Linux
Chuck Silvers Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
David Laight Re: fsync performance hit on 1.6.1
07/08/2003
Daniel Brewer Re: fsync performance hit on 1.6.1
Jochen Kunz Re: fsync performance hit on 1.6.1
Daniel Brewer Re: fsync performance hit on 1.6.1
Jochen Kunz Re: fsync performance hit on 1.6.1
gabriel rosenkoetter Re: fsync performance hit on 1.6.1
Kamal R Prasad Re: fsync performance hit on 1.6.1
David Laight Re: fsync performance hit on 1.6.1
Thomas Klausner Re: FYI: this time, really about to import crypto framework
der Mouse Re: fsync performance hit on 1.6.1
Matthias Buelow Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
Christos Zoulas Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
der Mouse Re: fsync performance hit on 1.6.1
07/09/2003
Matthias Buelow Re: fsync performance hit on 1.6.1
Matthias Buelow Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
der Mouse Re: fsync performance hit on 1.6.1
Christoph Hellwig Re: fsync performance hit on 1.6.1
Kamal R Prasad Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
Christoph Hellwig Re: fsync performance hit on 1.6.1
D'Arcy J.M. Cain Re: Is this kernel fault OK?
Christos Zoulas Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
Christoph Hellwig Re: fsync performance hit on 1.6.1
Matt Thomas Re: fsync performance hit on 1.6.1
Greg A. Woods POSIX shm_open() vs. mmap(MAP_ANON|MAP_SHARED)....
Matthias Buelow Re: fsync performance hit on 1.6.1
Matthias Buelow Re: fsync performance hit on 1.6.1
der Mouse Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
der Mouse Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
Greywolf Re: POSIX shm_open() vs. mmap(MAP_ANON|MAP_SHARED)....
der Mouse Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
der Mouse Re: fsync performance hit on 1.6.1
Greywolf Re: fsync performance hit on 1.6.1
07/10/2003
Christoph Hellwig Re: fsync performance hit on 1.6.1
Matthias Buelow Re: fsync performance hit on 1.6.1
Kamal R Prasad Re: fsync performance hit on 1.6.1
Greg A. Woods Re: fsync performance hit on 1.6.1
Kamal R Prasad Re: fsync performance hit on 1.6.1
Valeriy E. Ushakov Re: Dynamic linking is go (again)
Greg A. Woods Re: funlink() for fun!
Greg A. Woods Re: POSIX shm_open() vs. mmap(MAP_ANON|MAP_SHARED)....
Greg A. Woods Re: fsync performance hit on 1.6.1
Greywolf Re: funlink() for fun!
Matthew Mondor Re: fsync performance hit on 1.6.1
Greg A. Woods Re: funlink() for fun!
Greywolf Re: funlink() for fun!
Stephan Uphoff uvm_vslock / uvm_vsunlock problems
Greg A. Woods Re: funlink() for fun!
Greywolf Re: funlink() for fun!
Stephan Uphoff Re: uvm_vslock / uvm_vsunlock problems
der Mouse Re: funlink() for fun!
Bill Studenmund Re: Misc. pthread problems
Christian Limpach sa/pthread smp concurrency (includes patch)
07/11/2003
Reinoud Zandijk Misc. pthread problems
Simon Burge Re: uvm_vslock / uvm_vsunlock problems
Christian Limpach sa/pthread smp concurrency (includes patch)
Greg A. Woods Re: funlink() for fun!
der Mouse Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
der Mouse Re: funlink() for fun!
David Laight Re: uvm_vslock / uvm_vsunlock problems
David Laight Re: funlink() for fun!
Roland Dowdeswell Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Stephan Uphoff time traveling with physio
Greywolf Re: funlink() for fun!
Stephan Uphoff Re: uvm_vslock / uvm_vsunlock problems
der Mouse Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Greywolf Re: funlink() for fun!
Greywolf Re: funlink() for fun!
Greywolf Re: funlink() for fun!
07/12/2003
Matthias Buelow Re: funlink() for fun!
Matthias Buelow Re: funlink() for fun!
der Mouse Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
der Mouse Re: funlink() for fun!
Greywolf Re: funlink() for fun!
Greywolf Re: funlink() for fun!
joerg@britannica.bec Re: funlink() for fun!
Ignatios Souvatzis Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
der Mouse Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
07/13/2003
Emmanuel Dreyfus kernel malloc questions
David Laight Re: uvm_vslock / uvm_vsunlock problems
Matthias Buelow Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Chuck Silvers Re: time traveling with physio
Chuck Silvers Re: uvm_vslock / uvm_vsunlock problems
07/14/2003
Matthias Buelow Re: funlink() for fun!
Bill Studenmund Re: sa/pthread smp concurrency (includes patch)
Stephan Uphoff Re: uvm_vslock / uvm_vsunlock problems
Stephan Uphoff Re: time traveling with physio
Greg A. Woods Re: funlink() for fun!
Thor Lancelot Simon Re: sa/pthread smp concurrency (includes patch)
Greywolf Re: funlink() for fun!
Matthias Buelow Re: funlink() for fun!
Frank van der Linden Re: sa/pthread smp concurrency (includes patch)
Greg A. Woods Re: funlink() for fun!
Ben Harris Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Matthias Buelow Re: funlink() for fun!
Greywolf Re: funlink() for fun!
Matthias Buelow Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
Stephan Uphoff Re: sa/pthread smp concurrency (includes patch)
Greg A. Woods Re: funlink() for fun!
der Mouse Re: funlink() for fun!
Soren Jacobsen Re: very wierd behaviour
Greywolf Re: very wierd behaviour
Greywolf Re: funlink() for fun!
der Mouse Re: funlink() for fun!
Greg A. Woods Re: funlink() for fun!
der Mouse Re: funlink() for fun!
Matt Thomas Re: #ifdef DECNET
07/15/2003
Reinoud Zandijk very wierd behaviour
Reinoud Zandijk Re: very wierd behaviour
Christian Limpach Re: sa/pthread smp concurrency (includes patch)
matthew green re: funlink() for fun!
Jun-ichiro itojun Hagino #ifdef DECNET
Nick Hudson Re: sa/pthread smp concurrency (includes patch)
Kamal Prasad Availability
Keichii Moto How to print "Hello" using system call?
Hubert Feyrer Re: How to print "Hello" using system call?
Keichii Moto Re: How to print "Hello" using system call?
Hubert Feyrer Re: How to print "Hello" using system call?
Bill Studenmund Re: sa/pthread smp concurrency (includes patch)
Charles Blundell Re: How to print "Hello" using system call?
Bill Studenmund re: funlink() for fun!
Bill Studenmund Re: funlink() for fun!
Bill Studenmund Re: funlink() for fun!
Bill Studenmund Re: funlink() for fun!
ww@styx.org Re: funlink() for fun!
Bill Studenmund Re: funlink() for fun!
der Mouse Re: funlink() for fun!
Ignatios Souvatzis Re: funlink() for fun!
Bill Studenmund Re: funlink() for fun!
07/16/2003
Greg A. Woods Re: funlink() for fun!
Keichii Moto Re: How to print "Hello" using system call?
Love Re: How to print "Hello" using system call?
Love Re: How to print "Hello" using system call?
Keichii Moto Re: How to print "Hello" using system call?
Matt Fredette ancient ufs patch
07/17/2003
Nicolas Saurbier =?iso-8859-1?Q?FreeBSD=B4s_ioperm=28=29_vs=2E_NetBSD=B4s_i386=5Fset=5Fi?=
Dublet Re: FreeBSD?s ioperm() vs. NetBSD?s i386_set_ioperm()
Nicolas Saurbier AW: FreeBSD?s ioperm() vs. NetBSD?s i386_set_ioperm()
Tad Hunt how do I disable preemptive scheduling for the currently executing kproc?
Tad Hunt Re: how do I disable preemptive scheduling for the currently executing kproc?
der Mouse sequencer dropouts?
der Mouse Re: sequencer dropouts?
Jason Thorpe Re: how do I disable preemptive scheduling for the currently executing kproc?
07/18/2003
Frank van der Linden Re: how do I disable preemptive scheduling for the currently executing kproc?
Curt Sampson Supermicro Motherboard IDE Errors
Gavan Fantom Re: sequencer dropouts?
Jukka Marin Re: Supermicro Motherboard IDE Errors
Kamal R Prasad Re: Supermicro Motherboard IDE Errors
Ignatios Souvatzis Re: Supermicro Motherboard IDE Errors
Felix Deichmann Re: Supermicro Motherboard IDE Errors
Curt Sampson Re: Supermicro Motherboard IDE Errors
Simon Burge Re: Supermicro Motherboard IDE Errors
Thomas Klausner ogle
Havard Eidnes Fix for PR#20390 - callwheel corruption related to TCP
Patrick Welche Re: ogle
Thomas Klausner Re: ogle
Jason Thorpe Re: Fix for PR#20390 - callwheel corruption related to TCP
07/20/2003
Chuck Silvers Re: uvm_vslock / uvm_vsunlock problems
Chuck Silvers Re: time traveling with physio
Jason Thorpe Re: time traveling with physio
Alexander Yurchenko Re: Promise Ultra66/100 vs 48-bit LBA compliant drives
Chuck Silvers non-executable mappings
Jaromir Dolecek Re: ancient ufs patch
07/21/2003
Thomas Klausner software suspend
Ben Harris Re: non-executable mappings
Volker A. Brandt Re: software suspend
kpneal@pobox.com Re: rough SA patch (works on SMP)
Pankaj's Unix Account HP 88780B round tape drive
07/22/2003
Quentin Garnier Re: FYI: this time, really about to import crypto framework
Marton Fabo reconfigure ide controller?
YAMAMOTO Takashi EJUKEBOX/ETRYLATER
rick@snowhite.cis.uo EJUKEBOX
David Laight memory leak in pty code
Matthew Jacob Re: HP 88780B round tape drive
Jonathan Stone Re: FYI: this time, really about to import crypto framework
Jeremy C. Reed sleep and retry on ENOMEM (out of swap) instead of killing
Bill Studenmund Re: FYI: this time, really about to import crypto framework
Sam Leffler Re: FYI: this time, really about to import crypto framework
07/23/2003
YAMAMOTO Takashi Re: EJUKEBOX
itojun@iijlab.net Re: FYI: this time, really about to import crypto framework
itojun@iijlab.net Re: FYI: this time, really about to import crypto framework
Ben Harris Re: sleep and retry on ENOMEM (out of swap) instead of killing
Aaron J. Grier Re: kern/17107
07/25/2003
Jonathan Stone Re: FYI: this time, really about to import crypto framework
Sam Leffler Re: FYI: this time, really about to import crypto framework
Jonathan Stone Re: FYI: this time, really about to import crypto framework
07/26/2003
Jason Thorpe New i2c framework
07/27/2003
Dheeraj Reddy Question setting ethernet addresses on an interface
Juergen Hannken-Illjes Re: New i2c framework
Jason Thorpe Re: New i2c framework
Jaromir Dolecek RFC: g/c fuibyte(),fuiword(),suibyte(),suiword() ?
cgd@broadcom.com Re: RFC: g/c fuibyte(),fuiword(),suibyte(),suiword() ?
Jaromir Dolecek Re: Question setting ethernet addresses on an interface
07/28/2003
NOGUCHI Hiroshi atw driver and Host-AP mode
Robert Elz Re: RFC: g/c fuibyte(),fuiword(),suibyte(),suiword() ?
Zach Lowry Quesions concerning a new NetBSD Port
Ben Harris Re: New i2c framework
Brad du Plessis Probing ttyU?
Jason Thorpe Re: New i2c framework
Jonathan Stone Re: New i2c framework
Jason Thorpe Re: New i2c framework
Ben Harris Re: New i2c framework
Lennart Augustsson Re: Probing ttyU?
Jason Thorpe Re: New i2c framework
Jonathan Stone heads-up: hifn7751.c soon to be replaced
Matt Thomas crypto framework and dmover?
Artem Belevich kern/17107
Jason Thorpe Re: crypto framework and dmover?
Jonathan Stone Re: crypto framework and dmover?
07/29/2003
Daniel Carosone Re: Probing ttyU?
Kamal R Prasad profiling code
Jochen Kunz NetBSD Device Driver Writig Guide
Kamal R Prasad Re: profiling code
Juergen Hannken-Illjes namei(".") behaviour
Sam Leffler Re: crypto framework and dmover?
Juergen Hannken-Illjes Re: namei(".") behaviour
Eduardo Horvath Re: New i2c framework
Jason Thorpe Re: New i2c framework
Greywolf Re: namei(".") behaviour
Juergen Hannken-Illjes Re: namei(".") behaviour
Jason Thorpe Re: New i2c framework
07/30/2003
Thomas Klausner Re: New i2c framework
Kamal R Prasad Re: New i2c framework
Jason Thorpe Re: New i2c framework
Jason Thorpe Re: New i2c framework
cgd@broadcom.com Re: New i2c framework
Jesse Off usb umass broken for BUSlink?
07/31/2003
Lennart Augustsson Re: usb umass broken for BUSlink?
Jason Thorpe Re: New i2c framework
Eduardo Horvath Re: New i2c framework
Jason Thorpe Re: New i2c framework
Ming Lei how can kernel space expand to >1GB?
Nathan J. Williams Re: New i2c framework
Jason Thorpe Re: New i2c framework
Nathan J. Williams Re: New i2c framework
Jason Thorpe Re: how can kernel space expand to >1GB?
Eduardo Horvath Re: New i2c framework
Eduardo Horvath Re: New i2c framework
Jason Thorpe Re: how can kernel space expand to >1GB?
Ming Lei RE: how can kernel space expand to >1GB?
Jonathan Stone Re: how can kernel space expand to >1GB?
Ming Lei RE: how can kernel space expand to >1GB?
der Mouse Re: how can kernel space expand to >1GB?
der Mouse Re: how can kernel space expand to >1GB?
Stephan Uphoff Re: how can kernel space expand to >1GB?
Bryan P Re: how can kernel space expand to >1GB?
Ming Lei RE: how can kernel space expand to >1GB?
Ming Lei RE: how can kernel space expand to >1GB?
Gary Thorpe RE: how can kernel space expand to >1GB?