Searched refs:starved (Results 1 – 10 of 10) sorted by relevance
94 unsigned int starved; /* times reads have starved writes */ member402 (dd->starved++ >= dd->writes_starved)) in __dd_dispatch_request()418 dd->starved = 0; in __dd_dispatch_request()997 seq_printf(m, "%u\n", dd->starved); in deadline_starved_show()
157 unsigned long starved; member
2987 qs->rspq.starved++; in sge_timer_rx()
1308 goto starved; in scsi_target_queue_ready()1321 goto starved; in scsi_target_queue_ready()1325 starved: in scsi_target_queue_ready()1350 goto starved; in scsi_host_queue_ready()1364 goto starved; in scsi_host_queue_ready()1378 starved: in scsi_host_queue_ready()
62 be totally starved.
44 result in the ``rcu_.*kthread starved for`` console-log message,307 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,
4933 kthread is starved first, then the CPU.