From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org
Subject: [PATCH] b43: use rx desc underrun interrupt
Date: Sun, 21 Apr 2013 18:35:14 +0200 [thread overview]
Message-ID: <20130421183514.3f9799a7@milhouse> (raw)
In-Reply-To: <CAFzhf4rio-z1VSefBRWgm1yHhJ90tQM9K9pm6Q=--o6-ncS1Fg@mail.gmail.com>
On Sun, 21 Apr 2013 16:24:18 +0100
Piotras <piotras@gmail.com> wrote:
> >> Not sure if FIFO overruns are really an issue and how to prevent them.
> >> Maybe RX underflow should be handled in top half and reprogram device
> >> to suspend receives (is this possible)?
> >
> > What is "top half"?
>
> Top half interrupt handler (b43_do_interrupt).
No way.
Interrupts are properly blocked before leaving the top-half handler and
re-enabled before leaving the bottom-half handler already.
Adding stuff to the top-half handler would only introduce serious locking
and latency issues and it would fix nothing.
--
Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20130421/36056889/attachment.sig>
next prev parent reply other threads:[~2013-04-21 16:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 8:02 [PATCH] b43: use rx desc underrun interrupt Thommy Jakobsson
2013-04-19 14:32 ` Jonas Gorski
2013-04-19 15:55 ` Michael Büsch
2013-04-19 15:59 ` Jonas Gorski
2013-04-19 18:17 ` Larry Finger
2013-04-19 18:57 ` Michael Büsch
2013-04-19 20:37 ` Thommy Jakobsson
2013-04-19 20:46 ` Michael Büsch
2013-04-19 21:05 ` Larry Finger
2013-04-19 20:30 ` Thommy Jakobsson
2013-04-20 14:14 ` Thommy
2013-04-20 18:35 ` Larry Finger
2013-04-20 22:47 ` Thommy Jakobsson
2013-04-20 19:12 ` Michael Büsch
2013-04-20 19:47 ` Thommy Jakobsson
2013-04-20 19:50 ` Michael Büsch
2013-04-20 20:16 ` Thommy Jakobsson
2013-04-20 20:38 ` Michael Büsch
2013-04-20 20:56 ` Piotras
[not found] ` <CAFzhf4rSUO9mn_RKw4Vehw2LKggFdC_W0v-K_KKCZJez1AwynQ@mail.gmail.com>
2013-04-20 21:01 ` Thommy Jakobsson
2013-04-20 21:10 ` Thommy Jakobsson
2013-04-20 21:23 ` Thommy Jakobsson
2013-04-21 6:38 ` Michael Büsch
2013-04-21 8:22 ` Thommy Jakobsson
2013-04-21 8:44 ` Michael Büsch
2013-04-21 9:01 ` Thommy Jakobsson
2013-04-21 9:21 ` Michael Büsch
2013-04-21 12:12 ` Thommy Jakobsson
2013-04-21 14:46 ` Piotras
2013-04-21 14:59 ` Michael Büsch
2013-04-21 15:24 ` Piotras
2013-04-21 16:35 ` Michael Büsch [this message]
2013-04-21 15:11 ` Thommy Jakobsson
2013-04-21 16:31 ` Michael Büsch
2013-04-21 18:07 ` Thommy Jakobsson
2013-04-21 18:26 ` Michael Büsch
2013-04-21 18:44 ` Thommy Jakobsson
[not found] ` <CAOTQ16LCWpAOndQsHBxN1-X_8SLpcU8V=mM41gvcNRocA=GhsA@mail.gmail.com>
2013-04-21 18:44 ` Michael Büsch
2013-04-21 20:13 ` Thommy Jakobsson
2013-04-21 21:53 ` Michael Büsch
2013-04-22 8:11 ` Thommy Jakobsson
2013-04-22 10:00 ` Michael Büsch
2013-04-23 6:22 ` Michael Büsch
2013-04-21 14:27 ` Piotras
2013-04-21 14:51 ` Michael Büsch
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=20130421183514.3f9799a7@milhouse \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.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.