bsd/sys/buf.h

164  @discussion Will return truth after a buf_getblk that finds a valid buffer in the cache or the relevant
318  @discussion For buffers created through buf_getblk() (i.e. traditional buffer cache usage),
335  @discussion For buffers created through buf_getblk() (i.e. traditional buffer cache usage),
388  block number is normally set by the cluster layer or by buf_getblk().
397  @discussion Logical block number is set on traditionally-used buffers by an argument passed to buf_getblk(),
407  @discussion Physical block number is generally set by the cluster layer or by buf_getblk().
417  @discussion Logical block number is set on traditionally-used buffers by an argument passed to buf_getblk(),
526  buf_getblk() was passed a device vnode.  It is set on an iobuf if buf_alloc() is passed a device
536  @discussion A buffer's device is set in buf_strategy() (or in buf_getblk() if the file is a device).
548  through buf_getblk, it handles finding physical block numbers for the I/O (with VNOP_BLKTOOFF and
574  obtained with a buf_getblk().  If data has been read into core without using
700  i.e. by buf_getblk() and callers thereof. Unlike buf_invalblkno(), it can be made to write dirty data to disk
968  @function buf_getblk
970  @discussion buf_getblk() gets a buffer, not necessarily containing valid data, representing a block in a file.
973  buf_getblk() first looks for the buffer header in cache; if the buffer is in-core but busy, buf_getblk() will wait for it to become
979  return buffers obtained with buf_getblk().
990 buf_t	buf_getblk(vnode_t, daddr64_t, int, int, int, int);