On Fri, Oct 8, 2010 at 1:49 PM, Christian Lamparter <chunkeey@xxxxxxxxxxxxxx> wrote: > On Friday 08 October 2010 22:40:39 Luis R. Rodriguez wrote: >> On Fri, Oct 8, 2010 at 1:35 PM, Christian Lamparter >> <chunkeey@xxxxxxxxxxxxxx> wrote: >> > Several serve threading problems in the current >> > release reorder timer implementation have been >> > discovered. >> > >> > A lengthy discussion - which lists some of the >> > pitfalls and possible solutions - can be found at: >> > Âhttp://marc.info/?t=128635927000001 >> > >> > But due to the complicated nature of the subject and >> > the imminent advent of a new -rc cycle, it was >> > decided to disable the feature for the time being. >> > >> > Signed-off-by: Christian Lamparter <chunkeey@xxxxxxxxxxxxxx> >> >> This patch lacks documentation of the impact of this patch, while it >> may fix a lock issue, the does not address what happens when the patch >> is actually applied. > ? It just disables the timer. The actual reorder code > is left untouched, everything is the same as in Linus' > 2.6.36-rcX tree. > > Or what impact are you talking about? The timer is what I'm talking about, we don't run then ieee80211_release_reorder_timeout() right so we don't clear stale frames on aggregates. What impact does this have? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
