All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolai ZHUBR <zhubr@mail.ru>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Ivo van Doorn <ivdoorn@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re[2]: ieee80211_tx_status: headroom too small
Date: Sat, 31 Oct 2009 17:24:37 +0300	[thread overview]
Message-ID: <7724371.20091031172437@mail.ru> (raw)
In-Reply-To: <1256981677.3555.94.camel@johannes.local>

Saturday, October 31, 2009, 12:34:37 PM, Johannes Berg wrote:
>> > > 4 actually, wasn't there some cases where the header could have an odd
>> > > number of bytes and would require 3 bytes for alignment?
>> > 
>> > Hm, is there? I thought they changed the 11s draft to no longer have
>> > that.
>> 
>> Well 2 is fine in that case, (I was basing my comment on something said on this mailinglist
>> a long time ago). :)

> However, it really all depends on the hardware too ... Maybe we should
> put more of the logic into drivers, and have mac80211 only export its
> required headroom?

> Or maybe we should just not bother with having drivers do the alignment
> any more -- mac80211 does that now and it only does it if necessary
> (i.e. not on powerpc/x86)

I'm having this issue on mips platform, if it matters. I cannot test
it on x86 yet.

Now, searching for "extra_tx_headroom" gives me essentially the
following two:

net/mac80211/main.c:
        local->tx_headroom = max_t(unsigned int , local->hw.extra_tx_headroom,
                                   sizeof(struct ieee80211_tx_status_rtap_hdr));

drivers/net/wireless/rt*pci.c:
        rt2x00dev->hw->extra_tx_headroom = 0;

So, as a quick-and-dirty fix, should I replace "max_t(..." by "4 + max_t(..."
or "= 0" by "= 4" ?

Thank you!

Nikolai ZHUBR

> johannes



  parent reply	other threads:[~2009-10-31 14:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-30 20:00 ieee80211_tx_status: headroom too small Nikolai ZHUBR
2009-10-30 20:03 ` Luis R. Rodriguez
2009-10-30 20:49   ` Re[2]: " Nikolai ZHUBR
2009-10-30 20:59 ` Johannes Berg
2009-10-30 21:56   ` Re[2]: " Nikolai ZHUBR
2009-10-31  5:46     ` Johannes Berg
2009-10-31  8:51       ` Ivo van Doorn
2009-10-31  8:56         ` Johannes Berg
2009-10-31  8:59           ` Ivo van Doorn
2009-10-31  9:25             ` Johannes Berg
2009-10-31  9:30               ` Ivo van Doorn
2009-10-31  9:34                 ` Johannes Berg
2009-10-31  9:44                   ` Ivo van Doorn
2009-10-31 10:03                     ` Johannes Berg
2009-10-31 10:17                       ` Ivo van Doorn
2009-10-31 10:23                         ` Johannes Berg
2009-10-31 10:33                           ` Ivo van Doorn
2009-10-31 14:24                   ` Nikolai ZHUBR [this message]
2009-10-31 15:35                     ` Re[2]: " Johannes Berg
2009-10-31 17:42                       ` Re[4]: " Nikolai ZHUBR

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=7724371.20091031172437@mail.ru \
    --to=zhubr@mail.ru \
    --cc=ivdoorn@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.