All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	David Miller <davem@davemloft.net>,
	Dave Young <hidave.darkstar@gmail.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] b43: fix ieee80211_rx() context
Date: Sun, 11 Oct 2009 19:08:58 +0300	[thread overview]
Message-ID: <87y6nhoqud.fsf@purkki.valot.fi> (raw)
In-Reply-To: <1255276971.4095.241.camel@johannes.local> (Johannes Berg's message of "Sun\, 11 Oct 2009 18\:02\:51 +0200")

Johannes Berg <johannes@sipsolutions.net> writes:

>> > +	local_bh_disable();
>> >  	ieee80211_rx(dev->wl->hw, skb);
>> > +	local_bh_enable();
>> 
>> This is a bit awkward from drivers' point of view, we have to add the
>> same code to all mac80211 drivers using either SPI or SDIO buses.
>> 
>> What about adding a new inline function ieee80211_rx_ni() which would
>> disable bottom halves like above and call ieee80211_rx()? IMHO that's
>> easier for the driver developers to understand and also easier to
>> document ("use this function when calling from process context"). If
>> this is acceptable, I can create a patch.
>
> 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.)

But if you don't see any benefit from adding a new function, I'll drop
the idea. No need to complicate this anymore :)

-- 
Kalle Valo

  reply	other threads:[~2009-10-11 16:09 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 [this message]
2009-10-12  3:08       ` David Miller
2009-10-12  7:49         ` Kalle Valo
2009-10-12 12:29           ` Luciano Coelho
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=87y6nhoqud.fsf@purkki.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=davem@davemloft.net \
    --cc=hidave.darkstar@gmail.com \
    --cc=johannes@sipsolutions.net \
    --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 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.