* jamal <[EMAIL PROTECTED]> 2006-06-30 17:31 > Better to explain the reason for ifb first: > ifb exists initially as a replacement for IMQ. > 1) qdiscs/policies that are per device as opposed to system wide. > This now allows for sharing. > > 2) Allows for queueing incoming traffic for shaping instead of > dropping. > > In other wise, the main use is for multiple devices to redirect to it. > Main desire is not for it to redirect to any other ifb device or eth > devices. I actually tried to get it to do that, but run into issues > of complexity and and came up with decision to drop instead of killing > the machine. > Other than that, it can redirect to any other devices - but may still > not be meaningful.
Last time I'm asking. Why are packets dropped? You mentioned tc_verd is set to 0 leading to a invalid from verdict. Fact is that the from verdict is set to a meaningful value again at dev_queue_xmit() or ing_filter() so ifb_xmit() only sees valid values. tx locks of individual ifb devices are independant, why would it deadlock? Where is the packet exactly dropped? > I have been thinking of Herberts change of qdisc_is_running and this may > help actually. Help on what? - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
