From: Pavel Roskin <proski@gnu.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Guido Guenther <agx@sigxcpu.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [patch] at76_usb wireless driver
Date: Sun, 04 Mar 2007 22:33:34 -0500 [thread overview]
Message-ID: <1173065614.2670.20.camel@dv> (raw)
In-Reply-To: <1173052343.6131.24.camel@johannes.berg>
On Mon, 2007-03-05 at 00:52 +0100, Johannes Berg wrote:
> Wouldn't you just always have prism headers in monitor mode? All cards I
> know do that iirc. Or well, radiotap seems to be the format of fashion
> these days. I don't particularly like either :)
Sounds good. Radiotap is more flexible and better defined, but just
leaving prism headers for now would be fine.
> Not sure. I find that it messes up some things too. Maybe run Lindent,
> diff the original vs. the result and take the hunks you like.
Yes, something like that.
> > * istate should be accessed using atomic_set/atomic_read; locking is overkill
>
> atomic operations can be quite expensive too, but you probably know
> better if you need it or not.
Actually, it looks like we don't need them either. Atomic operations
are useful for counters or generally when data is read and written at
once. Simply reading and writing integers is atomic by design of any
sane and supported CPU.
The istate locks were causing complains from the lock checkers, and my
attempt to replace them with atomic operations silenced those
complaints. But It looks like we just need to drop those locks. They
were put there in a hurry without due checking, they don't address any
problem, but they may create one.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-03-05 3:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070110145724.GA4171@bogon.ms20.nix>
[not found] ` <20070223221230.GA9965@bogon.ms20.nix>
2007-03-03 15:00 ` [patch] at76_usb wireless driver Guido Guenther
2007-03-03 15:09 ` Johannes Berg
2007-03-03 15:18 ` Johannes Berg
2007-03-04 15:57 ` Guido Guenther
2007-03-03 16:23 ` Johannes Berg
2007-03-03 16:23 ` Johannes Berg
2007-03-04 7:09 ` Pavel Roskin
2007-03-04 23:52 ` Johannes Berg
2007-03-05 3:33 ` Pavel Roskin [this message]
2007-03-05 0:11 ` 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=1173065614.2670.20.camel@dv \
--to=proski@gnu.org \
--cc=agx@sigxcpu.org \
--cc=johannes@sipsolutions.net \
--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 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.