[RFTv2 3/5] ath10k: rework peer accounting

Kalle Valo kvalo at qca.qualcomm.com
Thu Apr 10 02:50:02 EDT 2014

Michal Kazior <michal.kazior at tieto.com> writes:

> It was troublesome to iterate over peers and
> perform sleepable calls. This will be necessary
> for some upcomming changes to tx flushing.
> Make peer allocation and initial setup
> protected by both ar->conf_mutex and
> ar->data_lock. This way it's possible to iterate
> over peers with conf_mutex and call sleepable
> functions.
> Signed-off-by: Michal Kazior <michal.kazior at tieto.com>

Sorry, but I'm not really getting your idea here of using both
conf_mutex and data_lock to protect ar->peers. Can you elaborate more,
please? Why can't we just use conf_mutex then? What am I missing?

Kalle Valo

More information about the ath10k mailing list