So does that mean that "tasklets", "work-queues" fall under this category and are triggered by "software Interrupt"? Regards,, Aravind. "Dovie'andi se tovya sagain" -Mat Cauthon (WoT). -----Original Message----- From: Tony Mouawad [mailto:tonym.ace@xxxxxxxxx] Sent: Thursday, October 25, 2007 6:19 PM To: Thippeswamy, Aravind Cc: kernelnewbies@xxxxxxxxxxxx Subject: Re: What is a "Software Interrupt"? "Software Interrupts" within the context of tasklets can also be called "Deferrable Functions". Generally how it works is that a device such as your ethernet card will trigger a "hardware interrupt" saying that there is data received. You will want to service hardware interrupts as quickly as possible so what you end up doing when you are handling your hardware interrupt is "schedule" a software interrupt or more appropriately schedule a function (defer a function) to handle this receive request at a moment outside of hardware interrupt handling. I think that would be the concept behind software interrupts around tasklets. Does that help? Tony. On 10/25/07, Thippeswamy, Aravind <AravindT@xxxxxxx> wrote: > > Hi, > What is a "Software Interrupt"? I was going thru the LDD 3 and > stumbled upon this. There is an > instance while explaining spin_lock_bh() function that the author > mentions that this only disables the "Software Interrupts"( LDD 3,page > number 119). In the immediately next paragraph, these "Software > Interrupts" are linked to "tasklets". I am not able to fully understand > this point. It would be really nice if some one elaborated on this. > > > > > > > > > Regards,, > > Aravind. > > > > "Dovie'andi se tovya sagain" > > -Mat Cauthon (WoT). > > -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
