public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: fix addba timer (again...)
Date: Wed, 18 Nov 2009 09:27:51 -0800 (PST)	[thread overview]
Message-ID: <alpine.LFD.2.01.0911180922120.4644@localhost.localdomain> (raw)
In-Reply-To: <1258560906.30511.43.camel@johannes.local>



On Wed, 18 Nov 2009, Johannes Berg wrote:
> 
> Linus pointed out that del_timer_sync() isn't actually needed if we make 
> the timer able to deal with no longer being needed when it gets queued 
> _while_ we're in the locked section that also deletes it. For that the 
> timer function only needs to check the HT_ADDBA_RECEIVED_MSK bit as well 
> as the HT_ADDBA_REQUESTED_MSK bit, only if the former is clear should it 
> do anything.

Ok, this looks sane. It's not really worth me Acking it, since I don't 
actually know the code or the hardware, so I can't really judge whether 
this is in any way a good thing.

But from a "design patterns" standpoint it no longer triggers my WTF 
reaction.

It's just bound to be more robust to have the timer just check the state 
of things itself rather than depend on some (complex and almost inevitably 
racy) "timer is only enabled IFF certain-state-is-true" rule.

			Linus

      reply	other threads:[~2009-11-18 17:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 16:15 [PATCH] mac80211: fix addba timer (again...) Johannes Berg
2009-11-18 17:27 ` Linus Torvalds [this message]

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=alpine.LFD.2.01.0911180922120.4644@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --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