Searched refs:starved (Results 1 – 16 of 16) sorted by relevance
88 unsigned int starved; /* times reads have starved writes */ member408 (dd->starved++ >= dd->writes_starved)) in __dd_dispatch_request()424 dd->starved = 0; in __dd_dispatch_request()995 seq_printf(m, "%u\n", dd->starved); in deadline_starved_show()
1312 goto starved; in scsi_target_queue_ready()1325 goto starved; in scsi_target_queue_ready()1329 starved: in scsi_target_queue_ready()1354 goto starved; in scsi_host_queue_ready()1368 goto starved; in scsi_host_queue_ready()1382 starved: in scsi_host_queue_ready()
157 unsigned long starved; member
2983 qs->rspq.starved++; in sge_timer_rx()
62 be totally starved.
44 result in the ``rcu_.*kthread starved for`` console-log message,284 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,
678 to ensure progress for potentially starved transactions (*note Progress
33568 this default should be used. For generally register-starved
4550 kthread is starved first, then the CPU.
5708 default should be used. For generally register-starved machines, such as\n\