linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kalle.valo@iki.fi>
Cc: Bob Copeland <me@bobcopeland.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	linville@tuxdriver.com
Subject: Re: drivers returning wrong results from their _tx op
Date: Fri, 09 Jan 2009 11:06:33 +0100	[thread overview]
Message-ID: <1231495593.3703.1.camel@johannes> (raw)
In-Reply-To: <87hc4828xn.fsf@litku.valot.fi> (sfid-20090109_091429_663068_48C13A9D)

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

On Fri, 2009-01-09 at 10:13 +0200, Kalle Valo wrote:

> > @@ -1170,6 +1170,7 @@ enum ieee80211_ampdu_mlme_action {
> >   *	configuration in the TX control data. This handler should,
> >   *	preferably, never fail and stop queues appropriately, more
> >   *	importantly, however, it must never fail for A-MPDU-queues.
> > + *	Returns NETDEV_TX_OK, or NETDEV_TX_BUSY if it fails.
> >   *	Must be implemented and atomic.
> 
> Based on discussion from netdev I have understood that NETDEV_TX_BUSY
> is not recommended, it's better to stop the queue already earlier,
> drop the frame or store the skb somewhere else temporarily. Johannes,
> have I understood this correctly?

Yes. Well, returning BUSY _should_ work, but I'd like to remove it and
the complicated retry logic from mac80211. Only adm8211 really needs it,
afaik, all other drivers can just drop the skb in error conditions,
adm8211 can only transmit one skb at a time so needs this for fragmented
frames which don't adhere to stopping the queue, unfortunately. This I
may change at some time.

johannes

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

  reply	other threads:[~2009-01-09 10:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-05 22:07 drivers returning wrong results from their _tx op Johannes Berg
2009-01-05 22:24 ` Bob Copeland
2009-01-06 13:00   ` Johannes Berg
2009-01-09  2:23     ` Bob Copeland
2009-01-09  8:13       ` Kalle Valo
2009-01-09 10:06         ` Johannes Berg [this message]
2009-01-09 15:44         ` Bob Copeland
2009-01-09 16:17           ` Kalle Valo
2009-01-09 18:27             ` Bob Copeland
2009-01-09 18:47               ` Kalle Valo
2009-01-11  3:12                 ` Bob Copeland
2009-01-11  6:21                   ` Kalle Valo

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=1231495593.3703.1.camel@johannes \
    --to=johannes@sipsolutions.net \
    --cc=kalle.valo@iki.fi \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=me@bobcopeland.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;
as well as URLs for NNTP newsgroup(s).