Searched refs:starvation (Results 1 – 18 of 18) sorted by relevance
9 lockless readers (read-only retry loops), and no writer starvation. They219 starvation (too much retry loops) in case of a sharp spike in write
138 writer starvation.303 thus preventing writer starvation.
70 u32 starvation[]; member
60 starvation.
85 each jumbo packet. This should help to avoid buffer starvation issues when
436 each jumbo packet. This should help to avoid buffer starvation issues when
337 each jumbo packet. This should help to avoid buffer starvation issues when
669 each jumbo packet. This should help to avoid buffer starvation issues when
85 SCHED_FIFO. But this caused other problems: SCHED_FIFO is not starvation
156 as its prone to starvation without deadline scheduling.
81 resources (e.g. to ensure that no application suffers from starvation) and/or to
286 to avoid starvation by heavy SCHED_OTHER background load.
274 tag starvation. Needed for some older devices
263 tag starvation. Needed for some older devices
441 - New CCB starvation avoiding algorithm.
337 - Simpler algorithm to deal with SCSI command starvation.
326 starvation case.
490 To avoid priority inversion through request starvation, a
