5 Commits

Author	SHA1	Message	Date
ambrisko	76dfd3add8	This will not compile without: ... http://www.ambrisko.com/doug/listio_kqueue/listio_kqueue.patch Note: it is a good idea to run this against a physical drive to exercise the physio fast path (ie. lio_kqueue /dev/<something safe>) This will ensure op's counting per LIO request is correct. It is currently broken the above patch fixes it. Sponsored by: IronPort	2005-03-02 04:00:55 +00:00
ambrisko	fd8046ee06	Add an AIO & kqueue regression test. It is a good idea to run this ... against a disk as the argument. If you don't it will use a temp file. The raw disk will use the kernel physio fast path method until the max number of pending op's is reached then it will queue them. File system op's are always queued. This is more important with LIO since operation can get split across and accounting of op's is broken with LIO. Note that this was broken when locking was added to kqueue (ie. 5.3) My fix needs to be better integrated with FreeBSD. Next is an LIO test and implementation. Sponsored by: IronPort	2005-03-02 03:32:01 +00:00
ru	cec60429bb	Start the dreaded NOFOO -> NO_FOO conversion. ... OK'ed by: core	2004-12-21 08:47:35 +00:00
rwatson	3522c0a675	Print a warning if running as !root for aio_md_test rather than failing ... the test. Privilege is required in order to allocate an md device.	2004-12-06 13:15:23 +00:00
rwatson	8bd5ca5854	Add a basic aio functionality regression test, which simply writes and ... then reads from a fairly broad range of object types: regular file, fifo, UNIX socketpair, pty, UNIX pipe, and an md device. Not a deep test of functionality, just a basic test that aio_write followed by aio_read returns the correct data in a relatively timely manner. Requested by: phk	2004-12-06 12:56:38 +00:00