The MPLS-OPS Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] [OT] leaky bucket
one basic question releated to the topic below.... what is the postulate behind leaky bucket algorithm and what does it apply to? the way i could make it out, leaky bucket says "water pours in at the rate it pours out else bucket overflows"... does this imply "if i dont have bandwidth in front, i cant cater to your packets (well it means sometime the queue will fill up)" does this imply that leaky bucket is not a problem to control packet flow rate..the bucket is only meant to decide what goes out 1st and what later..but i still cant oversubscribe bandwidth? so the leaky bucket is not a "queue", its a buffer (ideally there cant be a perpetual/non overflowing queue ever..)...... or that the buffer and queue are the same thing now? its a place i put my packets, play around with them and send them out...? so what is "leaky bucket" ..a buffer to play with packets but nothing else?..but no i want to use it as queue too........as i may have oversubscribed bandwidth....? does it also mean that i have to "fix" the bucket size in such a way that the quantum of packet sets which fits into the bucket and hence ensures no retransmission, is well defined? what is that "quantum of packet sets" which fall into the bucket without causing retransmissions? a window? would appreciate of someone could help here.......its a bit too woozy..... -rgds JS ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml
|
|