Searched hist:41674 (Results 1 - 2 of 2) sorted by relevance
| /freebsd-9.3-release/usr.sbin/iostat/ | ||
| H A D | iostat.c | diff 102068 Sun Aug 18 15:51:14 MDT 2002 bde Use essentially the same formatting of the CPU stats percentages as in vmstat so that they never coalesce. Both iostat and vmstat need larger fixes to prevent wide fields from unnecessarily messing up the alignment of all subsequent fields. PR: 41674 MFC-after: 3 days |
| /freebsd-9.3-release/sys/cam/scsi/ | ||
| H A D | scsi_sa.c | diff 41674 Fri Dec 11 05:19:36 MST 1998 mjacob Some fixes to handle fixed mode and variable mode more sensibly- and also incorporate some notion of which revision the device is. If it's < SCSI2, for example, READ BLOCK LIMITS is not a MANDATORY command. At any rate, the initial state is to try and read block limits to get a notion of the smallest and largest record size as well as the granularity. However, this doesn't mean that the device should actually *in* fixed block mode should the max && min be equal... *That* choice is (for now) determined by whether the device comes up with a blocksize of nonzero. If so, then it's a fixed block preferred device, otherwise not (this will change again soon). When actually doing I/O, and you're in fixed length mode, the block count is *not* the byte count divided by the minimum block size- it's the byte count divided by the current blocksize (or use shift/mask shortcuts if that worked out...). Then when you *change* the blocksize via an ioctl, make sure this actually propagates to the stored notion of blocksize (and update the shift/mask shortcuts). Misc Other: When doing a mode select, only use the SCSI_SAME_DENSITY (0x7f) code if the device is >= SCSI2- otherwise just use the saved density code. Recover from the ripple of ILLEGAL REQUEST not being 'retried' in that RESERVE/RELEASE is not a mandatory command for < SCSI2 (so ignore it if it fails). |
Completed in 62 milliseconds