From: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
To: "Linuxppc-Embedded@Lists. Linuxppc. Org (E-mail)"
<linuxppc-embedded@lists.linuxppc.org>
Subject: softirq context question
Date: Mon, 8 Dec 2003 11:48:04 +0100 [thread overview]
Message-ID: <000501c3bd78$c2c8f1a0$0a01a8c0@LUMENTIS02> (raw)
I have impl. NAPI for 8xx/enet.c. I choose to handle
TX IRQs in the poll() function as well. NAPI runs the packet
processing in softirq context.
All is working well, but I am a bit unsure about the locking rules
w.r.t softirq and scc_enet_start_xmit().
What is the difference between softirq context and hard irq context?
Can softirqs suspend scc_enet_start_xmit() or vice versa?
I have been running lots of flood ping tests without any locking at all
in scc_enet_start_xmit() and it works very well. This is no
comprehensive test and I have probably overlooked something.
Regards
Joakim
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-12-08 10:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='000501c3bd78$c2c8f1a0$0a01a8c0@LUMENTIS02' \
--to=joakim.tjernlund@lumentis.se \
--cc=linuxppc-embedded@lists.linuxppc.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 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).