> > +#define IEEE80211_TXCTL_AMPDU (1<<13) /* this frame should be sent
> > + * as part of an A-MPDU */
>
> Broadcom hardware will want to know
> (a) is this part of an A-MPDU
> (b) if so, is it
> (i) the first mpdu
> (ii) an intermediate mpdu
> (iii) the last mpdu
>
> Can we provide that easily and avoid the driver having to keep track?
well, this bit just tells the driver that this frame should be
aggregated. it does not, in any case, determines to low-level driver
what will be be distribution of frames per A-MPDU or the order of
them, as this is the low-level's driver/HW job. so i believe Braodcom
can do what iwlwifi do, just check this bit and decide if they
aggregate the frame or not, and in which A-MPDU. the rest of the
information needed can be extracted easily from start/stop aggregation
flows.
>
> > struct ieee80211_sched_data
> > {
> > + unsigned long qdisc_pool;
>
> If we ever have hw with many more queues we may want to increase
> NUM_TX_DATA_QUEUES_AMPDU, so if I understand the code correctly should
> be an array sized something like BITS_TO_LONGS(NUM_TX_...)
>
I can change this book keeping, though current solution provides us up
to 32 HW queues, which is really a huge amout of queues in terms of
HW. if needed after all, i would prefer to do it on top of this
series.
> johannes
>
>
-
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
