From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Linux Wireless" <linux-wireless@vger.kernel.org>
Subject: Re: Broken fragmentation
Date: Wed, 25 Jun 2008 12:50:10 +0300 [thread overview]
Message-ID: <1ba2fa240806250250k2ae66eddre00172f6bc871fcb@mail.gmail.com> (raw)
In-Reply-To: <1213910734.8967.117.camel@johannes.berg>
On Fri, Jun 20, 2008 at 12:25 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
>
>> >> Fragments are in the air but the peer is not able to reassemble them.
>> >> Something is wrong with the first fragment but I'm not sure yet.
>> >
>> > Hm, ok. got a packet capture? Maybe that was broken before, I remember
>> > having problems with fragmentation but putting it down to the
>> > known-to-be-completely-broken AP I was using.
>>
>> It is working the latest problem was caused by the driver, Yet i still
>> don't understand the regression
>> in the driver.
>
> Hmm, ok.
>
So the bug is still in mac80211. Fragments are scheduled to different
TIDs and hence to different queues.
Investigating further. If you have something in mind let me know
Thanks
Tomas
next prev parent reply other threads:[~2008-06-25 9:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 9:20 Broken fragmentation Tomas Winkler
2008-06-19 9:56 ` Johannes Berg
2008-06-19 11:46 ` Tomas Winkler
2008-06-19 11:57 ` Tomas Winkler
2008-06-19 12:23 ` Johannes Berg
2008-06-19 13:08 ` Tomas Winkler
2008-06-19 13:24 ` Johannes Berg
2008-06-19 14:45 ` Tomas Winkler
2008-06-19 15:26 ` Johannes Berg
2008-06-19 18:13 ` Tomas Winkler
2008-06-19 18:16 ` Johannes Berg
2008-06-19 21:09 ` Tomas Winkler
2008-06-19 21:25 ` Johannes Berg
2008-06-25 9:50 ` Tomas Winkler [this message]
2008-06-25 10:02 ` Johannes Berg
2008-06-25 10:30 ` Tomas Winkler
2008-06-25 10:32 ` Johannes Berg
2008-06-25 10:35 ` Tomas Winkler
2008-06-25 10:42 ` Johannes Berg
2008-06-25 10:59 ` Tomas Winkler
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=1ba2fa240806250250k2ae66eddre00172f6bc871fcb@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.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