From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Kalle Valo <kalle.valo@iki.fi>
Cc: David Miller <davem@davemloft.net>,
"johannes@sipsolutions.net" <johannes@sipsolutions.net>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"hidave.darkstar@gmail.com" <hidave.darkstar@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] b43: fix ieee80211_rx() context
Date: Mon, 12 Oct 2009 15:29:31 +0300 [thread overview]
Message-ID: <4AD3212B.4000503@nokia.com> (raw)
In-Reply-To: <87tyy5njbf.fsf@purkki.valot.fi>
ext Kalle Valo wrote:
> David Miller <davem@davemloft.net> writes:
>
>>>> I really don't see the point, since it's just three lines of code, but I
>>>> wouldn't mind all that much either.
>>> My worry are the developers who even don't know what is a bottom half
>>> and might get it all wrong. (Yes, there really are such people.)
>> And the difference between this and knowing you need to call the
>> ieee80211_rx_ni() thing is?
>>
>> You have to know what the heck a bottom half is to even know that you
>> would need to call the ieee80211_rx_ni() thing.
>>
>> And that's the same amount of knowledge necessary to simply wrap the
>> thing in a BH disable/enable sequence.
>
> I was thinking that it's possible to document it something like this:
>
> o in irq context use ieee80211_rx_irqsafe()
> o in a tasklet use ieee80211_rx()
> o in process context use ieee80211_rx_ni()
>
> Also in the future it might be easier to optimise something based on
> these functions. Maybe.
>
> But as Johannes didn't like the idea, and neither do you, I'm going to
> drop the idea. I'll add the BH disable/enable to wl1251 instead and
> hopefully Luciano does the same to wl1271.
Yeps, I can do the same for wl1271.
--
Cheers,
Luca.
next prev parent reply other threads:[~2009-10-12 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 10:19 [PATCH] b43: fix ieee80211_rx() context Johannes Berg
2009-10-11 10:26 ` Michael Buesch
2009-10-11 10:31 ` Johannes Berg
2009-10-11 10:35 ` Michael Buesch
2009-10-12 7:27 ` Holger Schurig
2009-10-11 10:39 ` David Miller
2009-10-11 11:53 ` Dave Young
2009-10-11 15:59 ` Kalle Valo
2009-10-11 16:02 ` Johannes Berg
2009-10-11 16:08 ` Kalle Valo
2009-10-12 3:08 ` David Miller
2009-10-12 7:49 ` Kalle Valo
2009-10-12 12:29 ` Luciano Coelho [this message]
2009-10-12 13:38 ` John W. Linville
2009-10-12 20:08 ` David Miller
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=4AD3212B.4000503@nokia.com \
--to=luciano.coelho@nokia.com \
--cc=davem@davemloft.net \
--cc=hidave.darkstar@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).