linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC] mac80211-hwsim:  support creating radios with specific name.
Date: Sat, 18 Oct 2014 09:00:39 -0700	[thread overview]
Message-ID: <54428EA7.8000302@candelatech.com> (raw)
In-Reply-To: <1413615195.10246.0.camel@jlt4.sipsolutions.net>



On 10/17/2014 11:53 PM, Johannes Berg wrote:
> On Fri, 2014-10-17 at 13:12 -0700, greearb@candelatech.com wrote:
>> From: Ben Greear <greearb@candelatech.com>
>>
>> Otherwise, it can be very difficult to know which is which
>> if you are trying to do detailed testing.
>
> Having just implemented something with dynamic radios in the
> wpa_supplicant test suite, I'm having second thoughts about this.
>
> When you create a new radio, it returns the hwsim identifier, which
> allows you to find the wiphy name in sysfs easily. Why not just rename
> it afterwards from userspace?

I plan to create (and recreate) thousands of these, and it will be less efficient to
have to rename each of them, as well as making user-space code more complex.

I too was looking at the hostap testing code, and the ability to specify names
of wiphy and the stations on creation time (as some of my other patches allow)
should simplify such testing, as well as my own testing needs.

I have patches to enable hostap to use the kernel features, but have not posted
them since kernel patches are still in flux.

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

      reply	other threads:[~2014-10-18 16:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 20:12 [RFC] mac80211-hwsim: support creating radios with specific name greearb
2014-10-18  6:53 ` Johannes Berg
2014-10-18 16:00   ` 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=54428EA7.8000302@candelatech.com \
    --to=greearb@candelatech.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 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).