On 2014-09-08 18:30, Rostislav Lisovy wrote: > The possible obstacles are: > * 802.11p will be used mainly for two independent C2X protocol stacks -- > one is the European ETSI ITS-G5, the other one is the US WAVE (IEEE > 1609). I assume that these two protocol stack implementations will > differ mainly in the user-space while the kernel part will be the same. > * ITS-G5 already speaks about the "default datarate" for different > channels ([1] 4.3, Table 2) -- i.e. 6 Mbit/s for channel no. 180; 12 > Mbit/s for channel no. 178. This should be probably defined when > "joining the network" on a fixed channel. > > The possible (first implementation) solution might be either to > implement some "dummy" rate control algorithm that will set a fixed > datarate only once (during "ocb join" command) or to use the Minstrel > while limiting the allowed datarate to be the lowest one; i.e. > mand_rates = ieee80211_mandatory_rates(sband, scan_width); > sta->sta.supp_rates[band] = > find_first_bit(&mand_rates, sizeof(u32)); > > If I am not mistaken, it is not possible to live without an in-kernel > rate_control algorithm? > One interesting idea I got from one colleague is to implement the > algorithm logic in the user-space -- kernel would contain just a thin > shell controlled from the user-space (via netlink?). This is probably > not as insane as it may sound since the purpose of the rate-control > algorithm for 802.11p (at least for ITS-G5) is not to "maximize the > immediate throughput" but more like "shared medium congestion control", > which may require much slower frequency of a control loop. I think doing this in userspace is overkill. minstrel should be able to handle rate control for 802.11p just fine if you set up the supported rates properly. By the way, minstrel does not try to "maximize the immediate throughput", it tries to maximize the ratio of throughput vs used airtime, which should be good for 802.11p as well. - Felix -- 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
