All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takeharu KATO <tkato@cs.fujitsu.co.jp>
To: linux-kernel@vger.kernel.org
Cc: linuxppc-dev@lists.linuxppc.org
Subject: [RFC] new feattures to improve linux interrupt response
Date: Thu, 07 Aug 2003 19:25:29 +0900	[thread overview]
Message-ID: <3F322919.AFFC7B6F@cs.fujitsu.co.jp> (raw)

Dear developers:

We have a plan to implement new features of Linux kernel for
embedded systems.
In particular, these features are planed to improve interrupt 
response on Linux. 
Please tell us whether someone has been engaged in 
working about the same features yet.
Of course any comments are welcome.
We describe the feature as follows. 

[1] Problems to be solved

We focus on the following problems to use Linux on the embedded systems.

(1) Long critical sections
	Linux has longer critical sections than RTOS.
	So the invocation of interrupt handler may be delayed until executions of 
	critical section 
	is ended for long time.	The issue declines the response time to interrupts.

(2) The handling order of interrupts is not guaranteed.
	Current Linux kernel does not guarantee the handling order of interrupts
 	, so any kind of interruptions can interrupt on  handlers
	which is not set SA_INTERRUPT flags.
	
	By the way, typically, when we design the systems, we assign the interrupt
	priority on each devices by its importance.
	(e.g. Some systems need to handle network devices before disk devices,
	other systems need to handle disk devices have most important priority.).
	These priorities are decided by the system's character. In such cases,
	developers need the mechanism to guarantee interruption handling order for
	their systems.
	

[2] The proposed features

	We are engaged in implementing following facilities.
	These features can be enabled/disabled by kernel configuration.
	If users disable these features in kernel configuration,
	our modification will make no effect on kernel behaviors.

	a) Quick interruption handling facility for embedded systems
		We are designing and implementing quick interrupt handling facility 
		for embedded systems. This is achieved by accepting some 
		interrupts(these are pre-defined in kernel configuration.) in current 
		Linux kernel's critical sections. 
		
		We will modify local_irq_disable/local_irq_enable macros
		to keep interrupt masks of some interrupts which need to handle quickly
		un-masked in most of kernel critical sections.
		
	b) Priority based interrupt handler facility
		We adopt interrupt priorities for interrupt handlers(top half handlers)
		to handle interruption orderly(like Solaris).  
		In current plan, these priorities are set in kernel configuration,
		so this feature will make no effects on  current interrupt handler
		handlers API (request_irq/free_irq and so on.). 
		
		This is achieved by invoking interrupt handlers by kernel threads.
		These threads are created for each priority. Interrupt 
		priority is represented by thread's priority.


[3] About target platform
We will implement these features on PowerPC 405GP(r) platform at first.

Sincerely, yours


-- 
Takeharu KATO
Fujitsu Limited
Email:tkato@cs.fujitsu.co.jp

             reply	other threads:[~2003-08-07 10:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 10:25 Takeharu KATO [this message]
2003-08-07 12:09 ` [RFC] new feattures to improve linux interrupt response Alan Cox

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=3F322919.AFFC7B6F@cs.fujitsu.co.jp \
    --to=tkato@cs.fujitsu.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.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.