Hi, some lapb network device drivers might currently call the interface routines to tha lapb protocol engine (in particular lapb_data_received()) from hardware irq. That causes problems with 2.4.0 so
With 3, there are two options a) the lapb module mantains an own backlog queue and schedules a tasklet that dequeues and processess the incoming frame. b) the lapb module creates a `pseudo' network i
David> I would recommend to do #3 but make it identical to David> lapb_data_received() except that it explicitly uses David> kfree_skb_irq(). Let the core networking "defer to Yes. My idea of #3 b w
As the input path of the lapb protocol is not trivial (it could even trigger additional output to acknowledge the revied frame), moving the whole protocol processing from hard irq to soft irq might b