From: Ben Greear <greearb@candelatech.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Arend van Spriel <arend@broadcom.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: mac80211-hwsim and tx-rates.
Date: Sat, 14 Mar 2015 11:04:33 -0700 [thread overview]
Message-ID: <55047831.8000307@candelatech.com> (raw)
In-Reply-To: <20150314174813.GA6772@localhost>
On 03/14/2015 10:48 AM, Bob Copeland wrote:
> On Sat, Mar 14, 2015 at 09:14:14AM -0700, Ben Greear wrote:
>> It can change with every packet based on rate-control logic, right?
>
> You said you wanted to go from index to bitrate -- the index changes,
> but not the rate<->index mapping.
The index means different things based on legacy, HT, VHT. You need index
+ flags to determine the actual rate for each packet.
I am fine with hard-coding in user-space the correlation of legacy index
to rates.
The array that is currently sent to user-space is the rates that rate-ctrl
determines should be used for transmit (and re-transmit), as far as I can tell.
>> And, it seems unlikely to me that an extra 16 bytes or so would make a
>> great deal of difference. Using hash tables instead of linear walks
>> and other things would likely improve performance more?
>
> Last time I tested with perf, memcpy dominated everything -- I've been
> thinking about having a mode where just headers are sent to userspace
> to avoid some of that.
I need full pkt in user-space, but at least for some use-cases your idea
may be a nice improvement.
With hundreds of virtual radios and network devices, hashing the lookup of
radios should be a big win. I'll work on that someday soon most likely.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2015-03-14 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 21:07 mac80211-hwsim and tx-rates Ben Greear
2015-03-11 21:31 ` Arend van Spriel
2015-03-11 22:06 ` Ben Greear
2015-03-14 10:47 ` Bob Copeland
2015-03-14 16:14 ` Ben Greear
2015-03-14 17:48 ` Bob Copeland
2015-03-14 18:04 ` Ben Greear [this message]
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=55047831.8000307@candelatech.com \
--to=greearb@candelatech.com \
--cc=arend@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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;
as well as URLs for NNTP newsgroup(s).