All of lore.kernel.org
 help / color / mirror / Atom feed
From: Parav Pandit <paravpandit@yahoo.com>
To: linuxppc-embedded@ozlabs.org
Subject: Locking interrupt handler in L1 cache
Date: Mon, 26 Feb 2007 20:59:17 -0800 (PST)	[thread overview]
Message-ID: <842614.52640.qm@web36603.mail.mud.yahoo.com> (raw)

[-- 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 --]

             reply	other threads:[~2007-02-27  5:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27  4:59 Parav Pandit [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-03-11 13:29 Locking interrupt handler in L1 cache Parav Pandit

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=842614.52640.qm@web36603.mail.mud.yahoo.com \
    --to=paravpandit@yahoo.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.