From: Andreas Hess <hess@tkn.tu-berlin.de>
To: linux-kernel@vger.kernel.org
Subject: Soft and Hard Interrupts
Date: Wed, 26 May 2004 16:52:23 +0200 [thread overview]
Message-ID: <200405261652.23367.hess@tkn.tu-berlin.de> (raw)
Hi,
I have difficulties in understanding the interplay between hard and soft
interrupts. Perhaps things get clearer with the following example:
1.) a packet is arriving at a NIC and triggers the execution of a hardware
interrupt
2.) the do_irq() routine is called
3.) the according interrupt service routine (ISR) is executed (which triggers
a soft interrupt)
4.) the kernel terminates the do_irq() routine and checks if there is a soft
interrupt waiting to be processed
5.) the soft interrupt is processed
The higher the arrival rate of packets, the higher the amount of interrupts to
be processed. In order to prevent the system from permanently processing
interrupts --- in case that a certain threshold value is reached --- the
ksoftirqd daemon takes over the responsibility for the software interrupt
handling. Then software interrupts are processed in the event that the
ksoftirqd is scheduled and running.
Is this so far correct? If yes, I wonder how the threshold value, the point at
which the ksoftirqd gets into charge, is defined?
Please 'CC' me as I am not subscribed to the list.
Thanks Andreas
reply other threads:[~2004-05-26 15:01 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=200405261652.23367.hess@tkn.tu-berlin.de \
--to=hess@tkn.tu-berlin.de \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®