From: "Tomas Winkler" <tomasw@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "John Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: move bss_conf into vif
Date: Sat, 11 Oct 2008 02:49:42 +0200 [thread overview]
Message-ID: <1ba2fa240810101749k5d053451kdaef3194a954b442@mail.gmail.com> (raw)
In-Reply-To: <1223685820.29811.23.camel@johannes.berg>
On Sat, Oct 11, 2008 at 2:43 AM, Johannes Berg
<johannes@sipsolutions.net> wrote:
> On Sat, 2008-10-11 at 02:32 +0200, Tomas Winkler wrote:
>> On Sat, Oct 11, 2008 at 1:51 AM, Johannes Berg
>> <johannes@sipsolutions.net> wrote:
>> > Move bss_conf into the vif struct so that drivers can
>> > access it during ->tx without having to store it in
>> > the private data or similar. No driver updates because
>> > this is only for when they want to start using it.
>>
>> What protection should driver take to be sure it won't be changed underneath ?
>> With prive copy you know this is changed only in bss_info changed is called.
>
> Yeah, that's true, I guess you can only access those fields there that
> you can access atomically. That's actually most of the fields though.
>
> Also, we don't actually take care about locking this structure at all
> even in mac80211, something we might need to think about.
When working on SM PS I have the same dilemma I have with
ieee80211_conf do you think I need to take a private copy of it?
Thanks
Tomas
>
> johannes
>
next prev parent reply other threads:[~2008-10-11 0:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 23:51 [PATCH] mac80211: move bss_conf into vif Johannes Berg
2008-10-11 0:32 ` Tomas Winkler
2008-10-11 0:43 ` Johannes Berg
2008-10-11 0:49 ` Tomas Winkler [this message]
2008-10-11 0:55 ` Johannes Berg
2008-10-11 0:56 ` 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=1ba2fa240810101749k5d053451kdaef3194a954b442@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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