| /test/stcnv/usr/src/tools/diskomizer/ |
| async.c | 84 struct async_work *work; member in struct:jobs
164 add_to_done(struct async_work *work)
168 work_done.head = work_done.tail = work;
171 work_done.tail->u.next = work;
172 work_done.tail = work;
174 work->flags |= ASYNCWORK_COMPLETE;
175 work->u.next = NULL;
179 do_work(struct async_work *work)
181 work->result = work->u.funcs.func(work->arg)
308 struct async_work *work; local
[all...] |
| async.h | 51 extern void * async_queue_request(struct async_work *work);
|
| daio_async.c | 41 struct async_work work; member in struct:daio_async
237 return (async_cancel_request(&x->work, 0));
285 x->work.u.funcs.func = (void * (*)(void *))do_daio_async_rw;
286 x->work.u.funcs.cancel = (int (*)(void *, int))do_daio_async_cancel;
287 x->work.arg = x;
288 x->work.flags = 0;
300 return (async_queue_request(&x->work) == NULL ? -1 : 0);
306 struct async_work *work; local
316 work = async_queue_wait(NULL, NULL, 0);
322 work = async_queue_wait(NULL, &abstime, 0)
[all...] |
| README | 61 Both build methods work with distributed make in parallel mode.
112 modules work correctly and can detect data corruption.
|
| /test/ohacts/src/tset/dataservice/doc/assertions/ |
| dataservice_reboot | 38 3. Failback property of the resource group should work as expected.
|
| /test/stcnv/usr/src/suites/nfs/nfsgen/tests/acl/ |
| README | 31 - trivial is to verify file/dir tools work well for acl.
|
| /test/ontest-stc2/src/suites/nfs/sharemnt/tests/nfslogd/ |
| README | 37 - the location of the private work buffer file.
64 arguments if work buffer and file handle file are not
|
| /test/stcnv/usr/src/suites/nfs/sharemnt/tests/nfslogd/ |
| README | 37 - the location of the private work buffer file.
64 arguments if work buffer and file handle file are not
|
| /test/ohacts/src/doc/dataservice/reboot/ |
| test_3.txt | 33 Failback property of the resource group should work as expected.
|
| /test/ohacts/src/doc/dataservice/ |
| testcases | 91 3. Failback property of the resource group should work as expected.
|
| /test/ontest-stc2/src/suites/net/nicdrv/doc/ |
| nicdrv.assert | 324 - After the testing, the test interface should still work (no hang).
378 - After 12-15 hours of testing, the test interface should still work
410 - After the testing, the test interface should still work (no hang).
|
| /test/stcnv/usr/src/suites/net/nicdrv/doc/ |
| nicdrv.assert | 324 - After the testing, the test interface should still work (no hang).
440 - After 12-15 hours of testing, the test interface should still work
472 - After the testing, the test interface should still work (no hang).
|
| /test/stcnv/usr/src/suites/os/cpu-caps/ |
| README | 35 zonecfg(1M), or via the project(4) file. CPU caps will work for all scheduling
|
| /test/stcnv/usr/src/suites/os/smf/ |
| README | 162 management scripts (pkgadd, pkgrm etc) and will not work with the IPS
|
| /test/ontest-stc1/usr/ontest/uts/fs/nfs/nfsv4-test/nfsv4shell/ |
| README | 39 This test client was inspired by previous work on a Tcl-based
185 way to work around it is to set the arguments as variables
|
| /test/ontest-stc2/src/suites/net/nc/ |
| README | 41 9. Future work
178 with this test suite otherwise they will not work because
279 9. Future work
|
| /test/ontest-stc2/src/tools/krb5tools/ |
| README | 45 These tools can work on either localhost or a remote host. If a host
376 variables, they should just work fine.
380 If that doesn't work for your domain, you
|
| /test/stcnv/usr/src/suites/nfs/nfsgen/ |
| README | 295 test environment, but they should work out of box and are not
337 - Some tests call ipfilter to block packets, but ipfilter doesn't work
353 *NOTE*: This section is intended only for people who work on
|
| /test/stcnv/usr/src/suites/nfs/nfsv4/nfsv4shell/ |
| README | 39 This test client was inspired by previous work on a Tcl-based
185 way to work around it is to set the arguments as variables
|
| /test/stcnv/usr/src/tools/krb5tools/ |
| README | 45 These tools can work on either localhost or a remote host. If a host
376 variables, they should just work fine.
380 If that doesn't work for your domain, you
|
| /test/stcnv/usr/src/tools/genutils/krb5tools/ |
| README.krb5tools | 45 These tools can work on either localhost or a remote host. If a host
378 directory. For all the others variables, they should just work fine.
382 If that doesn't work for your domain, you
|
| /test/ontest-stc2/src/suites/iSCSI/ |
| README | 39 1. A spare disk is required for this test suite to use for its work.
|
| /test/ontest-stc2/src/suites/os/smf/tests/svc.startd/doc/ |
| STARTD.README | 33 startd test cases involve the use of several components that work together
350 If that doesn't work then it will place the state in the file
|
| /test/stcnv/usr/src/suites/net/nc/ |
| README | 41 9. Future work
268 9. Future work
|
| /test/stcnv/usr/src/suites/os/smf/tests/svc.startd/doc/ |
| STARTD.README | 33 startd test cases involve the use of several components that work together
350 If that doesn't work then it will place the state in the file
|
