Lines Matching refs:pipe
216 bandwidth to different flows) and a "pipe", which essentially
218 pipe.
221 configurable. The "clock" for a pipe can come from either an
223 A pipe is also associated with one (or more, if masks are used)
224 queue, where all packets for that pipe are stored.
226 The bandwidth available on the pipe is shared by the queues
227 associated with that pipe (only one in case the packet is sent
238 There are three data structures definining a pipe and associated queues:
246 Multiple dn_flow_set can be linked to the same pipe, and multiple
261 wfq_ready_event() extract a pipe which in turn selects the right
262 flow using a number of heaps defined into the pipe itself.
317 * A dn_flow_set is created whenever a new queue or pipe is created (in the
333 struct dn_pipe *pipe ; /* pointer to parent pipe */
334 u_short parent_nr ; /* parent pipe#, 0 if local to a pipe */
387 struct dn_pipe { /* a pipe */
405 dn_key sched_time ; /* time pipe was scheduled in ready_heap */
487 user32_addr_t pipe ; /* pointer to parent pipe */
488 u_short parent_nr ; /* parent pipe#, 0 if local to a pipe */
525 struct dn_pipe_32 { /* a pipe */
543 dn_key sched_time ; /* time pipe was scheduled in ready_heap */
612 user64_addr_t pipe ; /* pointer to parent pipe */
613 u_short parent_nr ; /* parent pipe#, 0 if local to a pipe */
650 struct dn_pipe_64 { /* a pipe */
668 dn_key sched_time ; /* time pipe was scheduled in ready_heap */