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 09:14:14 -0700 [thread overview]
Message-ID: <55045E56.1050904@candelatech.com> (raw)
In-Reply-To: <20150314104742.GA13495@localhost>
On 03/14/2015 03:47 AM, Bob Copeland wrote:
> On Wed, Mar 11, 2015 at 03:06:18PM -0700, Ben Greear wrote:
>> I don't see a good way to tie that idx to an actual rate (which involves
>> flags, nss, mcs values, etc).
>>
>> Maybe I should also just send the info I care about, which is a 'bps' rate,
>> channel-width indication, SGI, etc as separate netlink attributes....
>
> My wmediumd fork (https://github.com/bcopeland/wmediumd) could benefit from
> this as well -- right now it assumes you use OFDM rates only.
>
> It probably makes sense to send the driver rate array as a separate
> netlink message though instead of in-band with CMD_FRAME, since it doesn't
> change per frame and amount of data sent over netlink in the datapath already
> imposes a performance limit.
It can change with every packet based on rate-control logic, right?
Possibly the power is mostly constant, but I thought I saw email about someone
working on rate-ctrl logic that adjusted power on a per-packet basis, so
thought it best to put in there now.
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?
>
> Is your simulator available somewhere?
No, sorry..it is a closed source thing that I am working on with another
company...even I do not have any real rights to the code. After a period
of time I may be able to start work on a similar simulator project, but for now all
I can contribute publicly is the kernel parts that must necessarily be open-source.
For what it's worth, the patch I posted seems to work with the user-space
app I've been working on.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2015-03-14 16:14 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 [this message]
2015-03-14 17:48 ` Bob Copeland
2015-03-14 18:04 ` Ben Greear
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=55045E56.1050904@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 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.