From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Ron Rindjunsky" <ron.rindjunsky@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlwifi and tx info in skb->cb
Date: Thu, 8 May 2008 02:29:09 +0300 [thread overview]
Message-ID: <1ba2fa240805071629i6c7336f6y61a7c9690820ef5e@mail.gmail.com> (raw)
In-Reply-To: <1210197711.3547.1.camel@johannes.berg>
On Thu, May 8, 2008 at 1:01 AM, Johannes Berg <johannes@sipsolutions.net> wrote:
> Hi,
>
> I was just trying to make iwlwifi work again with tx info in skb->cb,
> but am running into something I don't understand:
>
> What is a TFD, and why can it have multiple SKBs with a single tx
> status? I'm referring to:
TFD stands for TX File Descriptor
> /* One for each TFD */
> struct iwl3945_tx_info {
> struct ieee80211_tx_status status;
> struct sk_buff *skb[MAX_NUM_OF_TBS];
> };
>
> I would have expected something like this with 4965 that has aggregation
> support (and aggregation is reported just once) but here? Confused.
This is for scatter gather. Nothing to do with aggregation. If you get
fragmented frame you can send it out without linearizing in CPU. in
numer of TB - TX buffers (which is limitted bu MAX_NUM_OF_TBS) But
I'm just over ever explaining :)
Thanks
Tomas
> johannes
>
next prev parent reply other threads:[~2008-05-07 23:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-07 22:01 iwlwifi and tx info in skb->cb Johannes Berg
2008-05-07 23:29 ` Tomas Winkler [this message]
2008-05-07 23:30 ` Johannes Berg
2008-05-08 0:21 ` Tomas Winkler
2008-05-08 14:05 ` Johannes Berg
2008-05-08 22:07 ` Tomas Winkler
2008-05-08 22:10 ` Johannes Berg
2008-05-08 22:28 ` Tomas Winkler
2008-05-08 22:30 ` Johannes Berg
2008-05-08 23:16 ` Tomas Winkler
2008-05-08 23:17 ` Johannes Berg
2008-05-08 23:20 ` Johannes Berg
2008-05-08 23:20 ` David Miller
2008-05-08 23:30 ` 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=1ba2fa240805071629i6c7336f6y61a7c9690820ef5e@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=ron.rindjunsky@intel.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