Lines Matching refs:Request
37 information about request queue operations up to user space.
112 \item Time needed to insert or merge an incoming IO onto the request
120 for a request. That occurs between the Q and G operations. You
124 \item[Q2G] Time needed to \emph{get} a request (get request
127 \item[G2I] Time needed to put that request onto the request
131 For \emph{merged} requests -- an incoming request that is merged
132 with a previously submitted request -- we calculate \emph{Q2M}, the
135 \item Time spent on the request queue. The average time from when
136 the IO is inserted or merged onto the request queue, until it is
229 125 incoming requests into a single request down the IO stack. The
262 \item[Request Queue Plug Information]
265 such times the IO request queue elements are not able to be processed
266 by underlying drivers. The next section shows how often the request
275 There are two major reasons why request queues are unplugged, and both
279 \item Explicit unplug request from some subsystem in the kernel.
281 \item Timed unplugs, due to a request queue exceeding some temporal
290 In this subsection one can see the average number of IOs on the request
324 being held by the IO scheduler when an incoming IO request was being
531 being traced, that request queues Q and C traces are presented.
627 \item get request traces
