Searched refs:starved (Results 1 – 10 of 10) sorted by relevance
89 unsigned int starved; /* times reads have starved writes */ member396 (dd->starved++ >= dd->writes_starved)) in __dd_dispatch_request()412 dd->starved = 0; in __dd_dispatch_request()937 seq_printf(m, "%u\n", dd->starved); in deadline_starved_show()
157 unsigned long starved; member
2984 qs->rspq.starved++; in sge_timer_rx()
1295 goto starved; in scsi_target_queue_ready()1308 goto starved; in scsi_target_queue_ready()1312 starved: in scsi_target_queue_ready()1337 goto starved; in scsi_host_queue_ready()1351 goto starved; in scsi_host_queue_ready()1365 starved: in scsi_host_queue_ready()
62 be totally starved.
44 result in the ``rcu_.*kthread starved for`` console-log message,288 rcu_sched kthread starved for 23807 jiffies! g7075 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x1 ->cpu=5
215 traffic and the "slower" modem starved.
354 tasks will not be starved and the system might be able to respect all the456 tasks are not starved and that the tardiness of real-time tasks has an upper
46 register-starved machines. My discussions with Richard Outerbridge,
4705 kthread is starved first, then the CPU.
