On Sat, Jul 04, 2009 at 03:26:54PM +0200, thus spake Benoit PAPILLAULT:
quoted text
> That is the good questions :-). In fact, I think it has to do with
> Linux queue management which is something that is partially handled by
> the kernel (where the packets are stored in a queue) and the drivers
> (which reports if its hardware queue are full or not). Depending on
> your platform, when you set the xmit flags, it might consumes a lot of
> CPU and as such, break the CPU scheduling and as a consequence the
> queue scheduling.

Yeah well, I was thinking about that too and it may be the cause indeed. :/

quoted text
> What CPU are you using? Is it an embedded platform?

Core duo (first generation) T2400 clocked at 1.83GHz on a macbook pro (also
first generation), right at this time.

Maybe I should check whether simply commenting out the DPRINTFs regarding
ATH_DEBUG_XMIT still makes the xmit debug flag change anything.  I was also
wondering whether the setting of vap->iv_debug in ath_vap_create does
anything, but I doubt that function is called upon change of the debug flags
(and I'm always setting the xmit flag *after* setting the interface up).

-- 
If you're not living on the edge, you're taking up too much space.

------------------------------------------------------------------------------
_______________________________________________
Madwifi-devel mailing list
Madwifi-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/madwifi-devel