Searched refs:gaps (Results 1 – 15 of 15) sorted by relevance
61 - Ported document to Docbook XML, addition of DVBv5 API, documentation gaps fix.73 Most gaps between the uAPI document and the Kernel implementation
340 unsigned nsegs = 0, bytes = 0, gaps = 0; in bio_split_io_at() local361 gaps |= bvec_seg_gap(bvprvp, &bv); in bio_split_io_at()380 bio->bi_bvec_gap_bit = ffs(gaps); in bio_split_io_at()416 bio->bi_bvec_gap_bit = ffs(gaps); in bio_split_io_at()
109 subl $3*4, %esp # RET-IP + 3 gaps
50 any connected external receiver. This allows to avoid gaps
26 for some period, then looking for gaps in the TSC data. Any gap indicates a
80 will help programmers and sysadmins identify gaps in configuration
126 gaps of VA that don't need invalidation. This trades off impacted VA for number
30 be sparse - i.e. there may be gaps in the space with numbers where no
398 latest API changes. Closed gaps in the history chapter.
213 the process or driver which causes the scheduling gaps.
132 caller must leave gaps in the buffer for the storage of the confounder (if
64 includes unmapped gaps (though working on the intervening mapped areas),
352 detect if messages were dropped before reaching the target by identifying gaps
369 There are still a few gaps to be resolved to catch up with VFIO type1, as
35 zones are contiguous (there are no LBA gaps). Zones may have different types.