On Mon, Sep 26, 2011 at 03:45:53PM +0200, Stanislaw Gruszka wrote: > On Mon, Sep 26, 2011 at 07:34:41AM -0600, Felix Fietkau wrote: > > On 2011-09-26 6:23 AM, Rajkumar Manoharan wrote: > > >Recently mac80211 was changed to use nullfunc instead of probe > > >request for connection monitoring for tx ack status reporting > > >hardwares. These nullfunc data frames are being sent at higer > > >rates and also as aggregated ones. This could probably delays > > >the nullfunc ack so the connection is more frequently getting > > >disconnected as max retries are reached. In order to improve > > >the connectivity send the nullfunc at lower rate. > > I don't think nullfunc frames should be sent at the lowest rate. If > > they fail frequently, then the rate control module is doing > > something crappy and should be fixed. So far I haven't seen any > > nullfunc reliablity issues with minstrel_ht. > > Also, as far as I know, mac80211 sends non-QoS nullfunc frames, so > > they cannot get aggregated either. > > Perhaps nullfunc should be send at lowest rate only when it is > used for connection monitoring, but I'm not sure if we can easily > distinguish that. > I completely agree with you. If there are options to do that in simpler way, that could be the better solution :) -- Rajkumar -- 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
