netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Daniel Drake <dsd@gentoo.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
	netdev@vger.kernel.org, Stefano Brivio <st3@riseup.net>,
	John Linville <linville@tuxdriver.com>,
	Michael Buesch <mb@bu3sch.de>,
	Bcm43xx-dev@lists.berlios.de
Subject: Re: [PATCH] softmac: remove netif_tx_disable when scanning
Date: Sun, 26 Nov 2006 17:51:22 +0100	[thread overview]
Message-ID: <1164559882.22909.5.camel@johannes.berg> (raw)
In-Reply-To: <4569C2D0.8080406@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

On Sun, 2006-11-26 at 11:37 -0500, Daniel Drake wrote:

> However the other reason for the patch (transmit 
> queue needed for active scanning) is bogus,

I think that was just a misunderstanding.

> and the patch introduces a 
> problem where session frames may be transmitted during scanning (using 
> TX queue control avoids that problem).

Which is really the reason why we put that there in the first place :)

> Stack-level refcounted TX control like this would also be beneficial for 
> zd1211rw, currently we have a semi-ugly implementation inside the driver.

> I agree with the objectives of this patch but the way I see it is that 
> it trades one bug for another. A proper solution, as suggested by 
> Johannes (refcounted stack-level TX control) would not be hard to 
> implement and would solve the bug without introducing another.

Would you actually need a fully refcounted enable/disable? Because for
the stack it wouldn't be required if it'd simply not start scanning when
queue is disabled and stop scanning immediately when queue stop is
requested.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]

  reply	other threads:[~2006-11-26 16:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-26  0:16 [PATCH] softmac: remove netif_tx_disable when scanning Larry Finger
2006-11-26  4:05 ` Daniel Drake
2006-11-26 10:03   ` Johannes Berg
2006-11-26 12:12     ` Michael Buesch
     [not found]       ` <200611261312.20442.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-11-26 13:05         ` Larry Finger
     [not found]           ` <4569912C.1000506-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-11-26 13:06             ` Michael Buesch
     [not found]     ` <1164535408.21459.3.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2006-11-26 16:37       ` Daniel Drake
2006-11-26 16:51         ` Johannes Berg [this message]
     [not found]           ` <1164559882.22909.5.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2006-11-26 18:25             ` Daniel Drake
2006-11-26 18:40               ` Johannes Berg
     [not found]                 ` <1164566436.22909.26.camel-YfaajirXv214zXjbi5bjpg@public.gmane.org>
2006-11-26 19:03                   ` Larry Finger
2006-11-27  4:13                   ` Daniel Drake
2006-11-27 15:49         ` Michael Buesch
     [not found]   ` <45691273.9090803-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2006-11-26 10:07     ` Johannes Berg
2006-11-26 12:25   ` Michael Buesch

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=1164559882.22909.5.camel@johannes.berg \
    --to=johannes@sipsolutions.net \
    --cc=Bcm43xx-dev@lists.berlios.de \
    --cc=Larry.Finger@lwfinger.net \
    --cc=dsd@gentoo.org \
    --cc=linville@tuxdriver.com \
    --cc=mb@bu3sch.de \
    --cc=netdev@vger.kernel.org \
    --cc=st3@riseup.net \
    /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;
as well as URLs for NNTP newsgroup(s).