From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Radiotap <radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org>
Subject: Re: [RFA] HT extensions
Date: Tue, 05 Oct 2010 20:50:16 +0200 [thread overview]
Message-ID: <1286304616.3641.25.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20101005184252.GI14183-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
On Tue, 2010-10-05 at 13:42 -0500, David Young wrote:
> On Tue, Oct 05, 2010 at 08:27:43PM +0200, Johannes Berg wrote:
> > On Tue, 2010-10-05 at 13:21 -0500, David Young wrote:
> > > How can an application use the first/last-frame information?
> >
> > Well, right now my wireshark patch is simply displaying it, but it could
> > also link up frames of an a-MPDU so you can jump between them, and with
> > this it can know what the framing was. If you just know a frame was part
> > of an aMPDU you won't know which one, this should help.
>
> I have my doubts about that. How do you distinguish the case where the
> NIC gives you the first MPDU of A-MPDU 1 and the last MPDU of A-MPDU 2
> from the case where the NIC gives you the first and last MPDU of the
> same A-MPDU?
You mean with imperfect capturing? Otherwise you should've seen the last
of A-MPDU 1 inbetween that, I'd think. But you're right, doing this
perfectly is quite hard, and I don't really have a good use case in mind
either. I'm happy to leave it off, at least for now, until somebody can
demonstrate a working way to convey this information.
johannes
next prev parent reply other threads:[~2010-10-05 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 0:04 [RFA] HT extensions Johannes Berg
[not found] ` <1284595489.3707.54.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2010-09-21 15:46 ` Matteo Croce
2010-10-05 17:45 ` Johannes Berg
2010-10-05 18:21 ` David Young
[not found] ` <20101005182108.GH14183-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2010-10-05 18:27 ` Johannes Berg
[not found] ` <1286303263.3641.23.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2010-10-05 18:42 ` David Young
[not found] ` <20101005184252.GI14183-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2010-10-05 18:50 ` Johannes Berg [this message]
[not found] ` <1286304616.3641.25.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2010-10-05 18:56 ` David Young
[not found] ` <20101005185636.GJ14183-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org>
2010-10-06 9:23 ` Johannes Berg
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=1286304616.3641.25.camel@jlt3.sipsolutions.net \
--to=johannes-cdvu00un1vgdhxzaddlk8q@public.gmane.org \
--cc=radiotap-sUITvd46vNxg9hUCZPvPmw@public.gmane.org \
/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).