All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Felix Fietkau <nbd@openwrt.org>
Cc: linux-wireless@vger.kernel.org, linville@tuxdriver.com,
	lrodriguez@atheros.com
Subject: Re: [PATCH 1/2] mac80211: make ieee80211_send_bar available for drivers
Date: Wed, 10 Aug 2011 22:02:39 +0200	[thread overview]
Message-ID: <1313006559.4016.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1313005527-83182-1-git-send-email-nbd@openwrt.org>

On Wed, 2011-08-10 at 13:45 -0600, Felix Fietkau wrote:
> To properly maintain the peer's block ack window, the driver needs to be
> able to control the new starting sequence number that is sent along with
> the BlockAckReq frame.

I guess with the ath9k patch I understand ... I believe iwlwifi
processes all of the TX status and only sets the BAR flag on the last
one?

> +/**
> + * ieee80211_send_bar - send a BlockAckReq frame
> + *
> + * can be used to flush pending frames from the peer's aggregation reorder
> + * buffer.
> + *
> + * @vif: &struct ieee80211_vif pointer from the add_interface callback.
> + * @ra: the peer's destination address
> + * @tid: the TID of the aggregation session
> + * @ssn: the new starting sequence number for the receiver
> + */
> +void ieee80211_send_bar(struct ieee80211_vif *vif, u8 *ra, u16 tid, u16 ssn);

You might want to note the locking rules, it's a little strange here
since it calls right back into the driver's tx(). Though of course the
same also happens with tx_status(), it might be less expected here,
especially if you use tx_status_irqsafe() and this doesn't yet have an
irqsafe version.

johannes


  parent reply	other threads:[~2011-08-10 20:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 19:45 [PATCH 1/2] mac80211: make ieee80211_send_bar available for drivers Felix Fietkau
2011-08-10 19:45 ` [PATCH 2/2] ath9k: use ieee80211_send_bar to send BlockAckReq frames Felix Fietkau
2011-08-10 20:02 ` Johannes Berg [this message]
2011-08-10 21:17   ` [PATCH 1/2] mac80211: make ieee80211_send_bar available for drivers Felix Fietkau
2011-08-10 20:28 ` 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=1313006559.4016.1.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=nbd@openwrt.org \
    /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.