From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Gordon, Charles" <Charles.Gordon@digi.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Question on tx field of struct ieee80211_ops
Date: Thu, 22 Jan 2009 23:45:53 -0600 [thread overview]
Message-ID: <49795991.40507@lwfinger.net> (raw)
In-Reply-To: <8DCC153EAFE67A4B990A840E829F704B010A451E5DEF@mtk-sms-exch01.digi.com>
Gordon, Charles wrote:
> A follow up question on this is if my transmit routine does not have its own queue and the H/W can only transmit 1 packet at a time, should the transmit routine call ieee80211_stop_queue() when it starts the transmit procedure, and then call ieee80211_wake_queue() when the hardware indicates it has finished transmitting the packet.
I'm not an expert on mac80211, but if you look at the code in
drivers/net/wireless/rtl818x/rtl8187_dev.c, you will see that they TX
packets are not queued by the driver. When the tx ops routine is
called, the data is processed as required and the packet is sent on to
the hardware. In the callback routine, certain status information is
filled in and ieee80211_tx_status_irqsafe() is called to finish the
transaction. You only need to worry about protecting the private data
from concurrent access.
Larry
next prev parent reply other threads:[~2009-01-23 5:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-22 21:52 Question on tx field of struct ieee80211_ops Gordon, Charles
2009-01-22 22:26 ` Gordon, Charles
2009-01-23 5:45 ` Larry Finger [this message]
2009-01-23 22:10 ` Johannes Berg
2009-01-23 14:40 ` 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=49795991.40507@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Charles.Gordon@digi.com \
--cc=linux-wireless@vger.kernel.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 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).