Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

linux interrupt handler



On Mon, Jun 14, 2004 at 10:20:28AM -0400, paul.cour1 at verizon.net wrote:
> I am working on some IRQ handler code, and reading interrupt.h There is an expression "wrt" which I don't seem to be able
> to decode into a meaningful word (from my vocabulary).

"with respect to"

Nathan


> 
> 1. In the file interrupt.h there are some comments related to softirqs. Read this snippet and tell me what is inferred 
> by the reference to "wrt" ...
> 
> Comments from interrupt.h
> 
>  * If this tasklet is already running on another CPU 
>  * (or schedule is called
>  * from tasklet itself), it is rescheduled for later.
>  * Tasklet is strictly serialized wrt itself, but not  <----here?
>  * wrt another tasklets. If client needs some intertask
>  * synchronization, he makes it with spinlocks.
>  *
>  */
> 
> 
> 2. Googling around, I find the same expression "wrt" 
> referenced as below.
> BlockDev - You do (todo) 
> Open & Close - Mount & UnMount 
> request_handler 
> Loop thro the list of CURRENT requests 
> Merge clustered request (if you feel so) 
> Initiate DMA or so if any wrt device & Return  <----- this line ????
> interrupt_handler 
> end_request 
> Call request_handler 
> 
> thanks
> 
> paulc
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss
> 
> 

-- 




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org