Silly question: what about _always_ inserting requests in the second pass ?
It would take some more cpu (longer request queue to scan, but the whole
request queue is not very large), the requests would be inserted farther in
the queue but less likely to be delayed by new incoming requests so I guess the
time between insertion and execution would be roughly the same, and it should
solve the starvation problem (first pass, never modified, take a finite
time to be processed, and once it's done it's the second pass that is no longer
modified, ... so if request queue contains n requests, each request is
processed after less than n steps).
Best regards,
Pierre.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/