public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Arjan van de Veen <arjan@infradead.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Jon Masters <jonathan@jonmasters.org>,
	Sven Dietrich <sdietrich@suse.de>
Subject: Re: [RFC patch 0/5] genirq: add infrastructure for threaded interrupt handlers
Date: Thu, 02 Oct 2008 14:30:08 -0700	[thread overview]
Message-ID: <1222983008.2995.205.camel@laptop-eth> (raw)
In-Reply-To: <alpine.DEB.1.10.0810021652370.24442@gandalf.stny.rr.com>

On Thu, 2008-10-02 at 17:05 -0400, Steven Rostedt wrote:

> Why are you bringing up real time in this thread?? The thread has
> absolutely nothing to do with real time. This thread is about a better
> way to handle interrupt handlers.

I'm concerned about the connection between the two, which is what I'm
commenting on.

> > 
> > I also don't see a clear connection between these changes and ultimately
> > removing spinlock level latency in the kernel. I realize you don't
> > address that in your comments, but this is part of the initiative to
> > remove spinlock level latency..
> 
> Again, this thread has nothing to do with removing spinlock level latency.
> The reason Thomas did not address this is because it is OFF TOPIC!!!!

If they are connected (which I think we established) , then it's not out
of line for me to discuss the direction of these changes as related to
other components of real time.

> > 
> > So with this set of changes and in terms of real time, I'm wonder your
> > going with this ?
> 
> You brought in this relationship with real time, just because real time 
> uses threaded interrupts. This thread has nothing to do with real time. 
> That is what Ingo, Thomas and myself are trying to ge through to you.

You know Steven, often times you start a conversation and you have no
idea where it will end up.. You can't always control which direction it
will go..

> The strong reaction from Thomas is that you just brought up something that 
> is completely off topic.

We already debated this fact Steven. real time and this type of
threading are connected. It's not off topic to discuss connected
components.

If the intent here is to totally disconnect these threading patches from
any type of real time in the future, then that's a good answer to my
original question .. That these changes have no future what so ever in
regards to real time.

If they will be used in the future for real time then we should discuss
it. I don't think that's off topic at all.

> Basically, drop the real time topic from this thread. It's not related. 
> Yes real time addresses threaded interrupts, but just because we are 
> talking about threaded interrupts does not mean we are talking about real 
> time.

I don't see why you are so concerned with this.. Real time is taboo now?

Daniel


  reply	other threads:[~2008-10-02 21:30 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 23:02 [RFC patch 0/5] genirq: add infrastructure for threaded interrupt handlers Thomas Gleixner
2008-10-01 23:02 ` [RFC patch 1/5] genirq: make irqreturn_t an enum Thomas Gleixner
2008-10-01 23:02 ` [RFC patch 2/5] genirq: add a quick check handler Thomas Gleixner
2008-10-02  0:47   ` Jon Masters
2008-10-02  5:09     ` Steven Rostedt
2008-10-02 10:51       ` Jon Masters
2008-10-02 22:06         ` Greg KH
2008-10-02  4:52   ` Steven Rostedt
2008-10-03  8:29   ` Christoph Hellwig
2008-10-03 10:37     ` Thomas Gleixner
2008-10-01 23:02 ` [RFC patch 3/5] genirq: add threaded interrupt handler support Thomas Gleixner
2008-10-02  5:01   ` Steven Rostedt
2008-10-01 23:02 ` [RFC patch 4/5] genirq: add a helper to check whether the irq thread should run Thomas Gleixner
2008-10-01 23:02 ` [RFC patch 5/5] genirq: make irq threading robust Thomas Gleixner
2008-10-02  0:52   ` Jon Masters
2008-10-02  5:20     ` Steven Rostedt
2008-10-01 23:23 ` [RFC patch 0/5] genirq: add infrastructure for threaded interrupt handlers Andrew Morton
2008-10-01 23:29   ` Arjan van de Ven
2008-10-01 23:40     ` Andrew Morton
2008-10-01 23:58       ` Thomas Gleixner
2008-10-02  0:40 ` Jon Masters
2008-10-02 22:07   ` Greg KH
2008-10-08 22:18     ` Ingo Oeser
2008-10-02  1:53 ` Daniel Walker
2008-10-02 15:02   ` Steven Rostedt
2008-10-02 15:48     ` Daniel Walker
2008-10-02 18:42       ` Thomas Gleixner
2008-10-02 19:04         ` Daniel Walker
2008-10-02 19:23           ` Steven Rostedt
2008-10-02 19:28           ` Ingo Molnar
2008-10-02 20:09             ` Daniel Walker
2008-10-02 20:14               ` Steven Rostedt
2008-10-02 20:48                 ` Daniel Walker
2008-10-02 21:05                   ` Steven Rostedt
2008-10-02 21:30                     ` Daniel Walker [this message]
2008-10-02 22:28                       ` Steven Rostedt
2008-10-02 23:24                         ` Daniel Walker
2008-10-03  0:26                           ` Thomas Gleixner
2008-10-03 14:44                             ` Daniel Walker
2008-10-02 14:46 ` Andi Kleen
2008-10-02 21:31   ` Greg KH
2008-10-02 22:33     ` Arjan van de Ven
2008-10-03  3:25       ` Andi Kleen
2008-10-03  3:48         ` Arjan van de Ven
2008-10-03  4:35           ` Andi Kleen
2008-10-03  3:23     ` Andi Kleen
2008-10-21  1:32 ` [RFC patch] genirq threading for ehci, ohci and uhci USB hosts Sven-Thorsten Dietrich
2008-10-21  2:07   ` Jonathan Woithe
2008-10-21 10:29     ` [RFC patch] genirq threading (v2) for ehci, ohci and uhci USB hosts and ohci1394 Sven-Thorsten Dietrich

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=1222983008.2995.205.camel@laptop-eth \
    --to=dwalker@mvista.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=benh@kernel.crashing.org \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=sdietrich@suse.de \
    --cc=tglx@linutronix.de \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox