From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: linux-wireless@vger.kernel.org
Subject: changing dev->needed_headroom/needed_tailroom?
Date: Fri, 26 Jul 2013 16:50:10 +0200 [thread overview]
Message-ID: <1374850210.8248.59.camel@jlt4.sipsolutions.net> (raw)
Does it seem reasonable to change dev->needed_headroom and
dev->needed_tailroom on the fly?
We currently set needed_headroom to the max of what we need, but we
could do better like making it depend on the interface type (e.g. only
asking for mesh space on mesh interfaces). This would be done only when
the interface isn't connected, I can't promise it would be down but the
carrier would be off.
Another thing we might want to do is change it according to the
currently configured crypto (this would also affect
dev->needed_tailroom) since we actually only need tailroom when TKIP is
used. This could might be done on the fly, but could also be done when
the carrier is still down during connection establishment (which would
not be a complete optimisation but still be better than what we have
now)
Thoughts?
johannes
next reply other threads:[~2013-07-26 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 14:50 Johannes Berg [this message]
2013-08-02 8:55 ` changing dev->needed_headroom/needed_tailroom? Ben Hutchings
2013-08-02 13:11 ` Eric Dumazet
2013-08-05 14:00 ` Johannes Berg
2013-08-20 10:00 ` Florian Fainelli
2013-08-20 16:20 ` Stephen Hemminger
2013-08-20 16:24 ` Johannes Berg
2013-08-20 16:29 ` Stephen Hemminger
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=1374850210.8248.59.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).