From: Denis Kenzior <denkenz@gmail.com>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: [PATCH 1/3] hwsim: remove 'optimization' sending to only known MACs
Date: Wed, 28 Jun 2023 11:25:57 -0500 [thread overview]
Message-ID: <5b044364-7a3d-7be0-ff18-bcba656e6172@gmail.com> (raw)
In-Reply-To: <6795644d-1ce8-6937-d8b8-4318f2720289@gmail.com>
Hi James,
>>> Unfortunately once you move the radio into another namespace you lose any
>>> events associated with that radio, due to the PID of hwsim being associated
>>> with a distinct namespace (I think). So ADD/DEL_MAC_ADDR won't help here.
>>
>> Which events though? You should always be getting HWSIM_CMD_ events for _all_
>> radios since only a single hwsim instance is registered, no? Aren't these all
>> you need for the purposes of sending packets to the right radio?
>
> ADD/DEL_MAC_ADDR, which don't come once the radio is moved to another namespace
> (as far as I can tell with testing).
>
> I think it comes down to port ID:
>
> u32 _portid = READ_ONCE(data->wmediumd);
> ...
> hwsim_unicast_netgroup(data, skb, _portid);
Then this may be a conversation you have to start on linux-wireless. I would
have thought that there should only be a single wmediumd instance on a system
regardless of namespaces, but maybe I'm wrong here.
Regards,
-Denis
next prev parent reply other threads:[~2023-06-28 16:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 21:52 [PATCH 1/3] hwsim: remove 'optimization' sending to only known MACs James Prestwood
2023-05-04 21:52 ` [PATCH 2/3] test-runner: allow hwsim in namespaces James Prestwood
2023-05-04 21:52 ` [PATCH 3/3] test-runner: fix __str__ for namespace processes James Prestwood
2023-05-07 23:21 ` [PATCH 1/3] hwsim: remove 'optimization' sending to only known MACs Denis Kenzior
2023-05-08 13:43 ` James Prestwood
2023-05-08 18:05 ` Denis Kenzior
2023-05-08 18:55 ` James Prestwood
2023-05-08 19:00 ` Denis Kenzior
2023-05-08 19:03 ` James Prestwood
2023-05-08 19:01 ` Denis Kenzior
2023-06-21 21:05 ` James Prestwood
2023-06-27 2:31 ` Denis Kenzior
2023-06-27 15:15 ` James Prestwood
2023-06-27 18:00 ` Denis Kenzior
2023-06-27 18:56 ` James Prestwood
2023-06-27 19:23 ` Denis Kenzior
2023-06-27 20:09 ` James Prestwood
2023-06-28 14:49 ` Denis Kenzior
2023-06-28 15:33 ` James Prestwood
2023-06-28 15:40 ` Denis Kenzior
2023-06-28 16:14 ` James Prestwood
2023-06-28 16:25 ` Denis Kenzior [this message]
2023-06-28 16:47 ` James Prestwood
2023-06-28 16:57 ` Denis Kenzior
2023-06-28 17:22 ` James Prestwood
2023-06-28 23:19 ` Andrew Zaborowski
2023-06-28 23:28 ` James Prestwood
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=5b044364-7a3d-7be0-ff18-bcba656e6172@gmail.com \
--to=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.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