From: Ivo van Doorn <ivdoorn@gmail.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: "John Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, Michael Buesch <mbuesch@freenet.de>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH 1/2] d80211: Add software RTS support
Date: Mon, 5 Feb 2007 18:43:20 +0100 [thread overview]
Message-ID: <200702051843.20802.IvDoorn@gmail.com> (raw)
In-Reply-To: <20070205182808.2209ad3f@griffin.suse.cz>
On Monday 05 February 2007 18:28, Jiri Benc wrote:
> On Wed, 31 Jan 2007 20:16:50 +0100, Ivo van Doorn wrote:
> > Not all hardware are capable of generating their own RTS frames.
> > This patch will add support for creating the RTS frame in software,
> > when the driver requests this through the flag
> > IEEE80211_HW_SOFTWARE_RTS
>
> It seems this is not the ideal solution. Most of drivers needing
> software RTS would need to remember the RTS frame somewhere (as they
> need to pass it together with the actual frame).
Well in case of rt2x00 (I am not sure which other drivers also need software RTS)
the rts packet is just inserted inside the packet ring and is treated as a regular
packet/fragment that has just been inserted by the driver.
This patch just adds this additional packet just before the real packet, and in case
the real packet could not be send the rts packet is stored in the
ieee80211_tx_stored_packet structure to be send later.
> A better solution would be either to pass a pointer to RTS frame data
> in tx_control or to create a function returning RTS frame.
In case of rt2x00 this would deliver more problems, especially since it will use
a ring entry to send the rts frame and in case of rt2500usb and rt73usb it will
need a sk_buff structure since it needs to pass it to the device (where the sk_buff
will have some free tx_header_room for the descriptor.)
Ivo
next prev parent reply other threads:[~2007-02-05 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 19:16 [PATCH 1/2] d80211: Add software RTS support Ivo van Doorn
2007-02-05 17:28 ` Jiri Benc
2007-02-05 17:43 ` Michael Buesch
2007-02-05 18:08 ` Jiri Benc
2007-02-05 18:15 ` Ivo van Doorn
2007-02-05 18:23 ` Michael Buesch
2007-02-05 17:43 ` Ivo van Doorn [this message]
2007-02-05 17:47 ` Michael Buesch
2007-02-05 18:07 ` Ivo van Doorn
2007-02-05 18:22 ` Michael Buesch
2007-02-05 18:42 ` Ivo van Doorn
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=200702051843.20802.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linville@tuxdriver.com \
--cc=mbuesch@freenet.de \
--cc=netdev@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).