Locking interrupt handler in L1 cache

Locking interrupt handler in L1 cache

[Parav Pandit]

[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]

Hi,
  
  I have 8548 Linux based firewall which will mostly do packet processing for 80% time.
  So obviously most of the time it will RX and TX packets through gianfar ethernet driver.
  
  I want to lock my interrupt handler of this driver in the L1 cache.
  1. How can I use "icbtls" - Instruction Cache Block Touch and Lock Set" for locking my interrupt handler?
  
  2. Is "icbtls" is the correct instruction at which I am looking at?
  
  3. How do I find end address of the interrupt handler function and how  do we pass it to cache locking instructions? (Because it can happen  that interrupt handler size is more than a cache line, not aligned etc)?
  
  4. Can we enhance request_irq() function to take an additional parameter to lock the interrupt handler in the cache?
  
  I understand that if my interrupt handler is going to be called most of  the time then it is very likely to happen that OS will flush the same,  but there is no guarantee for it.
  
  Regards,
  Parav Pandit
  
 
---------------------------------
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.

[-- Attachment #2: Type: text/html, Size: 1327 bytes --]

Locking interrupt handler in L1 cache

[Parav Pandit]

Hi,

I have MPC 8548 Linux 2.6.x based firewall which will
mostly do packet processing for 80% time.
So obviously most of the time it will RX and TX
packets through gianfar ethernet driver.

I want to lock my interrupt handler of this driver in
the L1 cache.

1. Is there any kernel API for locking function and
data to lock them in the L1/L2 cache?

2. How can I use "icbtls" - Instruction Cache Block
Touch and Lock Set" for locking my interrupt handler?

3. Is "icbtls" is the correct instruction at which I
am looking at?

4. How do I find end address of the interrupt handler
function and how do we pass it to cache locking
instructions? (Because it can happen that interrupt
handler size is more than a cache line, not aligned
etc)?

5. Can we enhance request_irq() function to take an
additional parameter to lock the interrupt handler in
the cache?

I understand that if my interrupt handler is going to
be called most of the time then it is very likely to
happen that OS will flush the same, but there is no
guarantee for it.

Regards,
Parav Pandit



 
____________________________________________________________________________________
Get your own web address.  
Have a HUGE year through Yahoo! Small Business.
http://smallbusiness.yahoo.com/domains/?p=BESTDEAL