On Tue, 04 Dec 2007 18:40:47 +0100 Mattias Nissler <mattias.nissler@xxxxxx> wrote: > I don't think this data is useful for tuning the TX control algorithm at > all. In the case of a noisy channel, you can improve the rate of > successful transmission by switching to a more-robust rate. However, if > the driver just gets the parameters wrong, a slower rate won't help at > all, thus the feedback loop model on which the PID controller relies is > severely flawed. Well, I may object that here it looks like that setting a lower rate actually yields a lower failed frames ratio. But I agree with you, this data is suboptimal - at the very least - for helping us with tuning. > Ah, ok, module parameters show up in sysfs. This is good for testing, > but if we want to make some parameters available for everybody, we > cannot rely on module parameters, i.e. when mac80211 is compiled int the > kernel. I'd say we even want to be able to tweak the parameters on a per > device basis, we should really add them to mac80211 sysfs. Please see Johannes's proposal [1]. I tend to agree with that. Here comes my plan: for testing, I'd say we can stick to those modparams I introduced last night, setting perms to 644 and just being careful to bring down the interface before changing them through sysfs. When we're done with testing, we can decide which parameters need to be exported and which don't, and then implement proper locking and exporting parameters through nl80211. Is this OK for you? [1] Message-Id: <1196775624.6060.52.camel@xxxxxxxxxxxxx>, on linux-wireless. -- Ciao Stefano - 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
