linux软中断浅析.docxVIP

1、软中断软中断的原理就略过了，讲内核的书上都有，此处省略1500字。。。。。。1.1 注册还是以我最熟悉的两个老朋友做为开篇： open_softirq(NET_TX_SOFTIRQ, net_tx_action); open_softirq(NET_RX_SOFTIRQ, net_rx_action);open_softirq向内核注册一个软中断，其实质是设置软中断向量表相应槽位，注册其处理函数：void open_softirq(int nr, void (*action)(struct softirq_action *)){ softirq_vec[nr].action = action;}复制代码softirq_vec是整个软中断的向量表:struct softirq_action{ void? ? ? ? (*action)(struct softirq_action *);};static struct softirq_action softirq_vec[NR_SOFTIRQS] __cacheline_aligned_in_smp;复制代码NR_SOFTIRQS是最大软中断向量数，内核支持的所有软中断如下：enum{ HI_SOFTIRQ=0, TIMER_SOFTIRQ, NET_TX_SOFTIRQ, NET_RX_SOFTIRQ, BLOCK_SOFTIRQ, TASKLET_SOFTIRQ, SCHED_SOFTIRQ, HRTIMER_SOFTIRQ, RCU_SOFTIRQ,? ? ? ? /* Preferable RCU should always be the last softirq */ NR_SOFTIRQS};复制代码好像后为为RPS新增了一个，不过这我的内核版本偏低。1.2 激活?当需要调用软中断时，需要调用raise_softirq函数激活软中断，这里使用术语“激活”而非“调用”，是因为在很多情况下不能直接调用软中断。所以只能快速地将其标志为“可执行”，等待未来某一时刻调用。为什么“在很多情况下不能直接调用软中断”?试想一下下半部引入的理念，就是为了让上半部更快地执行。如果在中断程序代码中直接调用软中断函数，那么就失去了上半部与下半部的区别，也就是失去了其存在的意义。内核使用一个名为__softirq_pending的位图来描述软中断，每一个位对应一个软中断,位图包含在结构irq_stat中：typedef struct { unsigned int __softirq_pending; ……} ____cacheline_aligned irq_cpustat_t;DECLARE_PER_CPU_SHARED_ALIGNED(irq_cpustat_t, irq_stat);复制代码宏or_softirq_pending用于设置相应的位（位或操作）：#define or_softirq_pending(x)percpu_or(irq_stat.__softirq_pending, (x))复制代码local_softirq_pending用于取得整个位图（而非某一位）：#define local_softirq_pending()percpu_read(irq_stat.__softirq_pending)复制代码宏__raise_softirq_irqoff是or_softirq_pending的包裹：#define __raise_softirq_irqoff(nr) do { or_softirq_pending(1UL (nr)); } while (0)复制代码raise_softirq_irqoff通过调用__raise_softirq_irqoff实现激活软中断，它的参数nr即位软中断对应的位图槽位：/** This function must run with irqs disabled!*/inline void raise_softirq_irqoff(unsigned int nr){ //置位图，即标记为可执行状态 __raise_softirq_irqoff(nr); /*?* If were in an interrupt or softirq, were done?* (this also catches softirq-disabled code). We will?* actually run the softirq once we return from?* the irq or softirq.?*?* Otherwise we wake up ksoftirqd to make sure we?* schedule the softir