Searched hist:222228 (Results 1 - 5 of 5) sorted by relevance
| /freebsd-11-stable/sbin/hastctl/ | ||
| H A D | hastctl.c | diff 222228 Mon May 23 19:29:28 MDT 2011 pjd Keep statistics on number of BIO_READ, BIO_WRITE, BIO_DELETE and BIO_FLUSH requests as well as number of activemap updates. Number of BIO_WRITEs and activemap updates are especially interesting, because if those two are too close to each other, it means that your workload needs bigger number of dirty extents. Activemap should be updated as rarely as possible. MFC after: 1 week |
| /freebsd-11-stable/sbin/hastd/ | ||
| H A D | control.c | diff 222228 Mon May 23 19:29:28 MDT 2011 pjd Keep statistics on number of BIO_READ, BIO_WRITE, BIO_DELETE and BIO_FLUSH requests as well as number of activemap updates. Number of BIO_WRITEs and activemap updates are especially interesting, because if those two are too close to each other, it means that your workload needs bigger number of dirty extents. Activemap should be updated as rarely as possible. MFC after: 1 week |
| H A D | hast.h | diff 222228 Mon May 23 19:29:28 MDT 2011 pjd Keep statistics on number of BIO_READ, BIO_WRITE, BIO_DELETE and BIO_FLUSH requests as well as number of activemap updates. Number of BIO_WRITEs and activemap updates are especially interesting, because if those two are too close to each other, it means that your workload needs bigger number of dirty extents. Activemap should be updated as rarely as possible. MFC after: 1 week |
| H A D | secondary.c | diff 222228 Mon May 23 19:29:28 MDT 2011 pjd Keep statistics on number of BIO_READ, BIO_WRITE, BIO_DELETE and BIO_FLUSH requests as well as number of activemap updates. Number of BIO_WRITEs and activemap updates are especially interesting, because if those two are too close to each other, it means that your workload needs bigger number of dirty extents. Activemap should be updated as rarely as possible. MFC after: 1 week |
| H A D | primary.c | diff 222228 Mon May 23 19:29:28 MDT 2011 pjd Keep statistics on number of BIO_READ, BIO_WRITE, BIO_DELETE and BIO_FLUSH requests as well as number of activemap updates. Number of BIO_WRITEs and activemap updates are especially interesting, because if those two are too close to each other, it means that your workload needs bigger number of dirty extents. Activemap should be updated as rarely as possible. MFC after: 1 week |
Completed in 123 milliseconds