From: Johannes Berg <johannes@sipsolutions.net>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211_hwsim: add frame transmission support over virtio
Date: Thu, 05 Mar 2020 15:14:27 +0100 [thread overview]
Message-ID: <eab92ed50b403437786244b664a99f04e341ecc1.camel@sipsolutions.net> (raw)
In-Reply-To: <E37B1033-8525-422A-AF10-5EEE5988FE57@holtmann.org>
On Thu, 2020-03-05 at 15:09 +0100, Marcel Holtmann wrote:
>
> can we just make it a Kconfig option that defaults to 2, but gets set
> to 0 when virtio support is included.
We could, I guess, but I don't understand why?
I don't understand why you think there should be any relation between
virtio and the number of fake radios?
Basically, hwsim works like this:
There are a number of virtual radios (defaulting to two), which can
communicate with each other. This communication can be
1) handled inside the hwsim driver itself, "perfect" medium simulation
without any latency etc.
2) handled over netlink with wmediumd (running inside the same kernel),
i.e. calling out to userspace for all frame transmissions etc.
With this patch, in addition, the communication can be
3) handled over virtio to wmediumd running *outside* the qemu (untested)
or user-mode-linux virtual machine.
So you still need virtual radios inside, and virtio doesn't *create* any
new virtual radios, it just provides the wmediumd communication
mechanism. Regardless of virtio, you can have any number of virtual
radios inside the kernel.
johannes
next prev parent reply other threads:[~2020-03-05 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 13:32 [PATCH] mac80211_hwsim: add frame transmission support over virtio Johannes Berg
2020-03-05 13:59 ` Marcel Holtmann
2020-03-05 14:03 ` Johannes Berg
2020-03-05 14:09 ` Marcel Holtmann
2020-03-05 14:14 ` Johannes Berg [this message]
2020-03-05 14:18 ` Marcel Holtmann
2020-03-05 14:20 ` Johannes Berg
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=eab92ed50b403437786244b664a99f04e341ecc1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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