vfs whitebox test
Anybody already pull together some more closely interactive way of trying creative patterns of calls thru the vfs layer?
I ask because I'm still hung up on my demo that udf.ko can't reliably write more than one file at a time:
http://marc.theaimsgroup.com/?l=linux-fsdevel&m=106676214111422
List: linux-fsdevel
Subject: Re: zeroes read back more often than appended
Date: 2003-10-21 18:44:54
I'm guessing what makes that demo tough to analyse is that I wrote it up at the high level of fopen/ fwrite/ fclose/ hexdump. I'm guessing translating that demo down to the more verbose level of open/ write/ read/ close actually won't make the demo significantly easier to analyse. I'm thinking I have to drop down to the vfs level.
Can I somehow drop down to the vfs level?
Maybe I could run the fs as a .so?
Can I help in any way quicker than deciphering the source of udf.ko?
Pat LaVarre
Quoted 4 lines
Anybody already pull together some more closely interactive way of trying creative patterns of calls thru the vfs layer?
From the linux-fsdevel 2003-10-07 archives "Re: fs test suite", we know
possibilities, perhaps sorted now from most to least accessible, include:
http://ltp.sourceforge.net/
http://www.iozone.org
http://www.connectathon.org/
http://www.codemonkey.org.uk/cruft/
http://www.zip.com.au/~akpm/linux/patches/stuff/
http://www.google.com/search?q=postmark+linux
http://www.google.com/search?q=bonnie+linux
By now I can testify that at a glance these particular links do Not say if they point only to ways of running up in the stratospheric layer of open/ read/ write/ close, or not.
Pat LaVarre
Quoted 3 lines
Anybody already pull together some more
closely interactive way of trying creative
patterns of calls thru the vfs layer?
I read contents/ index/ pages at random and then sequentially the first two-hundred ninety-two pages of the German-flavoured English (e.g. "smaller than zero") of "Linux Kernel Internals" and then I saw:
gdb /usr/src/linux/vmlinux /proc/kcore
... "all the structures in the kernel to be read, but no local variables [also] not possible to change values or call kernel functions ..."
Also I saw:
- CFLAGS= -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer
+ CFLAGS= -Wall -Wstrict-prototypes -O2 -g
CFLAGS -g I find in linux-2.6.0-test9/Makefile near CONFIG_DEBUG_INFO.
grep CONFIG_DEBUG_INFO find . -name 'Kconfig'
then flunks, but that question I can pursue in ?l=kernelnewbies.
Pat LaVarre
On 25 Nov 2003 10:04:56 -0700 Pat LaVarre <[email protected]> wrote:
| > Anybody already pull together some more | > closely interactive way of trying creative | > patterns of calls thru the vfs layer? | | I read contents/ index/ pages at random and then sequentially the first | two-hundred ninety-two pages of the German-flavoured English (e.g. | "smaller than zero") of "Linux Kernel Internals" and then I saw: | | gdb /usr/src/linux/vmlinux /proc/kcore | | ... "all the structures in the kernel to be read, but no local variables | [also] not possible to change values or call kernel functions ..." | | Also I saw: | | - CFLAGS= -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer | + CFLAGS= -Wall -Wstrict-prototypes -O2 -g | | CFLAGS -g I find in linux-2.6.0-test9/Makefile near CONFIG_DEBUG_INFO. | | grep CONFIG_DEBUG_INFO `find . -name 'Kconfig'` | then flunks, but that question I can pursue in ?l=kernelnewbies.
search for DEBUG_INFO in all Kconfig files. They don't include the CONFIG_ prefix.
--
~Randy
MOTD: Always include version info.
Quoted 8 lines
gdb
/usr/src/linux/vmlinux/proc/kcore... "all the structures in the kernel to be read, but no local variables [also] not possible to change values or call kernel functions ..."
...grep
CONFIG_DEBUG_INFOfind . -name 'Kconfig'
then flunks, but that question I can pursue in ?l=kernelnewbies.
Whoops, sorry, by now I see what works is such slightly different syntax as:
grep -i CONFIG.SMP find . -name 'Kconfig' grep -i CONFIG.PREEMPT find . -name 'Kconfig' grep -i CONFIG.DEBUG_INFO find . -name 'Kconfig'
For example:
$ grep -i CONFIG.USB_STORAGE_DEBUG `find . -name 'Kconfig'` ./drivers/usb/storage/Kconfig:config USB_STORAGE_DEBUG $
Pat LaVarre
Quoted 6 lines
Quoted 4 lines
gdb
/usr/src/linux/vmlinux/proc/kcore... "all the structures in the kernel to be read, but no local variables [also] not possible to change values or call kernel functions ..."
...
grep -i CONFIG.DEBUG_INFOfind . -name 'Kconfig'
make xconfig --> "Kernel hacking" forces the pair:
+ CONFIG_DEBUG_KERNEL=y
+ CONFIG_DEBUG_INFO=y
Also I accepted the suggestions:
+ CONFIG_DEBUG_SLAB=y
+ CONFIG_MAGIC_SYSRQ=y
While still testing at random in hope of discovering something relevant, I should also try the slow DEBUG_PAGEALLOC, also DEBUG_STACKOVERFLOW.
Pat LaVarre
On 25 Nov 2003 08:46:22 -0700 Pat LaVarre <[email protected]> wrote:
| > Anybody already pull together some more closely interactive way of | > trying creative patterns of calls thru the vfs layer? | | >From the linux-fsdevel 2003-10-07 archives "Re: fs test suite", we know | possibilities, perhaps sorted now from most to least accessible, | include: | | http://ltp.sourceforge.net/
fsstress e.g.
Lots of file I/O, little VFS metadata activity.
| http://www.connectathon.org/ | | http://www.codemonkey.org.uk/cruft/
fsx-linux in particular
| http://www.zip.com.au/~akpm/linux/patches/stuff/ | | http://www.google.com/search?q=postmark+linux
postmark typically works with many small files and does more VFS metadata operations than a workload like IOzone or tiobench (sf.net).
| http://www.google.com/search?q=bonnie+linux | | By now I can testify that at a glance these particular links do Not say | if they point only to ways of running up in the stratospheric layer of | open/ read/ write/ close, or not.
--
~Randy
MOTD: Always include version info.
Quoted 4 lines
... ltp ... fsstress ...
... iozone ... Lots of file I/O, little VFS metadata activity. ... cruft ... fsx-linux in particular
... postmark ... many small files... more ... metadata ...
Guidance! Thank you. In particular, as I carry these links forward hopefully now instead I will remember to say:
http://www.codemonkey.org.uk/cruft/fsx-linux.c
At first glance in fsx-linux.c I think I see command line "usage" defined to produce open/ close/ read/ write/ lseek/ mmap/ munmap sequences.
Pat LaVarre
P.S. Also thank you I picked up:
http://www.google.com/search?q=tiobench+sf.net
http://tiobench.sourceforge.net/
http://sourceforge.net/projects/tiobench/
self-described as: "portable, robust, fully-threaded I/O benchmark program".