From: Ivo van Doorn <ivdoorn@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Add RTNL version of ieee80211_iterate_active_interfaces
Date: Tue, 6 May 2008 23:07:32 +0200 [thread overview]
Message-ID: <200805062307.32504.IvDoorn@gmail.com> (raw)
In-Reply-To: <1210099386.3914.21.camel@johannes.berg>
On Tuesday 06 May 2008, Johannes Berg wrote:
>
> > + * requested configurations, make sure to use
> > + * the _rtnl version since the regular version
> > + * requires atomic context.
>
> That's a bit misleading, the regular version requires that the callback
> is atomic :)
Ok, will fix.
> > + */
> > + rtnl_lock();
> > + ieee80211_iterate_active_interfaces_rtnl(rt2x00dev->hw,
> > + rt2x00lib_intf_scheduled_iter,
> > + rt2x00dev);
> > + rtnl_unlock();
>
> > /**
> > + * ieee80211_iterate_active_interfaces_rtnl - iterate active interfaces
> > + *
> > + * This function iterates over the interfaces associated with a given
> > + * hardware that are currently active and calls the callback for them.
> > + * This function allows the iterator function to sleep, the caller is
> > + * responsible for proper locking mechanisms to prevent concurrency.
>
> That description seems misleading. Also, since the mac80211 internal
> list management could possibly change (I don't see it changing but who
> knows), I think I'd prefer if this function acquired the rtnl itself
Ok, that is what I prefered as well, but the patch reverted it to the
original version ;)
> didn't have rtnl in the name. Can't think of a good name right now,
> maybe rename the other one to _atomic?
Ok, will fix.
Ivo
next prev parent reply other threads:[~2008-05-06 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 17:43 [PATCH] mac80211: Add RTNL version of ieee80211_iterate_active_interfaces Ivo van Doorn
2008-05-06 18:43 ` Johannes Berg
2008-05-06 21:07 ` Ivo van Doorn [this message]
2008-05-06 21:50 ` [PATCH v2] " Ivo van Doorn
2008-05-06 21:50 ` 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=200805062307.32504.IvDoorn@gmail.com \
--to=ivdoorn@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 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.