block: row: Remove warning massage from add_request
Regular priority queues is marked as "starved" if it skipped a dispatch due to being empty. When a new request is added to a "starved" queue it will be marked as urgent. The removed WARN_ON was warning about an impossible case when a regular priority (read) queue was marked as starved but wasn't empty. This is a possible case due to the bellow: If the device driver fetched a read request that is pending for transmission and an URGENT request arrives, the fetched read will be reinserted back to the scheduler. Its possible that the queue it will be reinserted to was marked as "starved" in the meanwhile due to being empty. CRs-fixed: 517800 Change-Id: Iaae642ea0ed9c817c41745b0e8ae2217cc684f0c Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
This commit is contained in:
parent
b3fe3ae918
commit
a19db032ca
|
@ -396,7 +396,6 @@ static void row_add_request(struct request_queue *q,
|
|||
"added urgent request (total on queue=%d)",
|
||||
rqueue->nr_req);
|
||||
rq->cmd_flags |= REQ_URGENT;
|
||||
WARN_ON(rqueue->nr_req > 1);
|
||||
rd->pending_urgent_rq = rq;
|
||||
}
|
||||
} else
|
||||
|
|
Loading…
Reference in New Issue