>Sorry, almost dropped this thread - my bad. > >> > > [Manikanta] Hmmm, I would like to have ieee80211_tx_status_8023 >> > > for now and go with a TODO for single tx reporting mechanism for >> > > both Ethernet and 802.11 tx formats. Any thoughts? >> > >> > There's an additional wrinkle btw - we currently report the 802.11 >> > frame to the monitor interface, if active. Not sure we can keep >> > that, but it's something to think about. >> > >> >> [Manikanta] Good point, this is something we have to think about. I >> believe this one is tricky, do we need to add the .11 header just >> before giving to monitor interfaces? > >It's complicated. The interface has radiotap+802.11 type, so on the one hand it >should have 802.11 header. On the other hand, having what went to the >hardware can be helpful. However, I don't think we can get around the >radiotap+802.11 type in any way. > >> How important will this be for Ethernet tx changes? I am running out >> of thoughts. > >Well I think it's something we should consider when we look at this path. >Hopefully nobody who really cares about performance has the monitor stuff >active - although we're thinking of ways to push down filters to make that less >expensive. > >Johannes
[Manikanta] Thanks for your time in reviewing the patch Johannes, I will make the changes as discussed and send out the next revision of the patch. -- Manikanta
