netdev - Re: [PATCH 1/2] d80211: Add software RTS support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 5 Feb 2007 19:08:34 +0100
From:	Jiri Benc <jbenc@...e.cz>
To:	Michael Buesch <mb@...sch.de>
Cc:	Ivo van Doorn <ivdoorn@...il.com>,
	"John Linville" <linville@...driver.com>, netdev@...r.kernel.org,
	Michael Buesch <mbuesch@...enet.de>,
	Johannes Berg <johannes@...solutions.net>
Subject: Re: [PATCH 1/2] d80211: Add software RTS support

On Mon, 5 Feb 2007 18:43:06 +0100, Michael Buesch wrote:
> I also think that sending RTS in software is not going to work,
> as the timing can not be guaranteed. And timing is why we do it in
> the first place. If the HW is not capable of sending RTS frames, we
> should not try to emulate them in SW, as it might make the situation
> even worse by messing up the NAVs by wrong timing.

That's not emulation in the software, it's just similar approach as
with sending fragmented frames - you need (more or less) precise timing
there as well and many cards still want them enqueued one-by-one. The
firmware takes care of the precise timing. The same could apply to RTS
frames (i. e. the firmware recognize them and doesn't send them before
it has the next frame ready).

 Jiri

-- 
Jiri Benc
SUSE Labs
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html