> > > The AC has first hand only to do with the access priority > to the air, > > but as a consequence the order of packets is only guaranteed within > > each AC. So each AC needs an individual TID and as a result an > > individual sequence number counter in order to do the duplicate > > detection. > > This is a bit confusing to me, I don't think each AC has a > TID, rather more than one TIDs map into a single AC. That is true. You cannot map packets with the same TID to several AC queues. The reason is retransmission. Each TID stream has to be mapped to one AC. My understanding from the previous email was different. > > > The atheros way is for sure possible but it comes with some > > constraints in building the aggregates. > > > > a) You can not dynamically adapt the A-MPDU to the remaining TXOP. > > b) You need to start a retransmission process of the > aggregate packets in > > the AC queue immediatly, because otherwise you cannot release the > > buffers. > > I wouldn't be so sure about either of these, Atheros hardware > has an elaborate scheme for suppressing frames and asking > software to requeue them to the hardware at a later time. I > suspect they can use it here to adapt the A-MPDU to the TXOP > and suppress the remaining MPDUs if they need to, and tell > the driver which of the aggregate packets needs to be retried > later. I suppose that would need fairly shallow DMA queues, > but that's doable. > > johannes > You are right, with software requeue of frames you get rid of the retransmission problem. With the tailoring of the A-MPDU to the TXOP I am more concerned of not having enough packets. In order to have some efficient aggregation you need to collect a number of packets but you have to make sure that if you have just one packet that you release it after some waiting time. Regards Friedrich -- 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
