CVS log for emstar/fusd/test/torturetest.c
	Help

Request diff between arbitrary revisions / Display revisions graphically / Jump to LXR

added the copyright notice to all the source code in the cens repository

- added a copyright notice to all the source code files in the cens
repository

Cleaned up some old fusd regression tests, and added a new one (in the
form of a packetdev torture test)

changed wait time slightly to handle high device loads better

Merged in the new FUSD from the main development branch

made torturtest automatic with appropriate retvals

Did a lot of work in trying to optimize the scheduling of fusd drivers
and the processes using them.

In the kernel: the driver now immediately yields the processor when
it completes a syscall.

In the user-space library: we now try to read as many fusd messages as
possible in fusd_dispatch() before giving up; thanks to the new
yielding in the module, it is very likely (when doing bulk data
transfer) that the app will issue another syscall before the driver's
next read.  This minimizes the number of context switches and syscalls
and increased speed by about 50%.  In particular, bulk data transfers
look (to the driver) like a long series of successful reads; no select
or even blocking on read in between!

We also now (optionally) use wake_up_interruptible_sync instead of plain
wake_up_interruptible in cases when we know we are about to yield to
another process.

fusd_run has been changed to take no args and return no retval; it
simply runs forever doing a fusd_dispatch on any readable FDs.  Meant
to be the simplest of "simple" interfaces.  Changed many example
programs to use the new fusd_run().

Changed kfusd.c default debug level from 10 to 2

Changed __VERYSAFE__ to __FUSD_VERYSAFE__

*** empty log message ***

fixed bug in fusd_run()

fixed bug in fusd_run()

using fusd_run() now

new torture test
fixed bugs in fusd_run

added locks for correctness

reversed comparison

new torturetest`:x