From 75ed29a57b8d99739afe31c847492b4f15abbad3 Mon Sep 17 00:00:00 2001 From: Yangjing Zhang Date: Fri, 13 May 2016 13:58:26 +0800 Subject: [PATCH] Update interrupts-9.md --- interrupts/interrupts-9.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/interrupts/interrupts-9.md b/interrupts/interrupts-9.md index e8d813a..a7b0ece 100644 --- a/interrupts/interrupts-9.md +++ b/interrupts/interrupts-9.md @@ -49,7 +49,7 @@ The `spawn_ksoftirqd` function starts this these threads. As we can see this fun early_initcall(spawn_ksoftirqd); ``` -Deferred interrupts are determined statically at compile-time of the Linux kernel and the `open_softirq` function takes care of `softirq` initialization. The `open_softirq` function defined in the [kernel/softirq.c](https://github.com/torvalds/linux/blob/master/kernel/softirq.c): +Softirqs are determined statically at compile-time of the Linux kernel and the `open_softirq` function takes care of `softirq` initialization. The `open_softirq` function defined in the [kernel/softirq.c](https://github.com/torvalds/linux/blob/master/kernel/softirq.c): ```C @@ -61,7 +61,7 @@ void open_softirq(int nr, void (*action)(struct softirq_action *)) and as we can see this function uses two parameters: -* the index of the `softirq_vec` array; +* the index of the `softirq_vec` array; * a pointer to the softirq function to be executed; First of all let's look on the `softirq_vec` array: