From: Johannes Berg <johannes@sipsolutions.net>
To: Manikanta Pubbisetty <mpubbise@qti.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Vasanthakumar Thiagarajan <vthiagar@qti.qualcomm.com>
Subject: Re: [RFCv2 2/2] mac80211: Implement data xmit for 802.11 encap offload
Date: Fri, 31 Mar 2017 13:52:19 +0200 [thread overview]
Message-ID: <1490961139.6288.10.camel@sipsolutions.net> (raw)
In-Reply-To: <fbc82bc9af344237bd5cd3210d9d012e@aphydexm01f.ap.qualcomm.com>
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
next prev parent reply other threads:[~2017-03-31 11:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 11:33 [RFCv2 0/2] Add new transmit data path for ethernet frame format mpubbise
2017-03-03 11:33 ` [RFCv2 1/2] mac80211: Add provision for 802.11 encap offload mpubbise
2017-03-03 12:29 ` Johannes Berg
2017-03-08 15:49 ` Pubbisetty, Manikanta
2017-03-03 11:33 ` [RFCv2 2/2] mac80211: Implement data xmit " mpubbise
2017-03-03 12:39 ` Johannes Berg
2017-03-08 15:46 ` Pubbisetty, Manikanta
2017-03-08 21:33 ` Johannes Berg
2017-03-09 9:56 ` Pubbisetty, Manikanta
2017-03-14 14:11 ` Johannes Berg
2017-03-21 5:36 ` Manikanta Pubbisetty
2017-03-31 11:52 ` Johannes Berg [this message]
2017-04-11 6:06 ` Manikanta Pubbisetty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1490961139.6288.10.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mpubbise@qti.qualcomm.com \
--cc=vthiagar@qti.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).