public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manu Abraham <abraham.manu@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew de Quincey <adq_dvb@lidskialf.net>
Subject: Re: [RFC] Simple userspace interface for PCI drivers
Date: Thu, 31 Aug 2006 17:24:30 +0400	[thread overview]
Message-ID: <44F6E30E.7010501@gmail.com> (raw)
In-Reply-To: <20060831001742.GB26265@kroah.com>

Greg KH wrote:
> On Thu, Aug 31, 2006 at 02:50:55AM +0400, Manu Abraham wrote:
>> Greg KH wrote:
>>> On Wed, Aug 30, 2006 at 09:07:44PM +0400, Manu Abraham wrote:
>>>> Being a bit excited and it is really interesting to have such a
>>>> proposal, it would simplify the matters that held us up even more,
>>>> probably. The name sounds fine though. All i was wondering whether there
>>>> would be any high latencies for the same using in such a context. But
>>>> since the transfers would occur in any way, even with a kernel mode
>>>> driver, i think it should be pretty much fine.
>>> As mentioned, this framework is being used in industrial settings right
>>> now, where latencies are a huge issue.  It works just fine, so I do not
>>> think there are any problems in this area.
>> Cool.
>>
>> Is there some way we can avoid the poll ? It would be a real gain
>> indeed, if a POLL can be avoided.
> 
> Use the signal that will be sent to your userspace program when an
> interrupt happens.
> 


Ok, that said, If we had RT signalling, that would have been a quantum leap.


> If you can handle the small latency that causes it should be fine, but
> if you can't, then you should be using poll :)
> 

hmm.. having a choice does always hurt your brain. ;-)


> It all depends on the hardware you are using, your processor, and what
> your tolerances are on your interrupt handling latency.


Usually in the typical application we have (where latency is an issue),
most probably many of the people have a saturated PCI bus. In most
cases, the IPTV guys have such a scenario. Say > 6 or 7 DVB adapters and
the latency goes very high. What i have seen is that when the bus gets
saturated, the CPU usage shoots of rather abnormally. When the latency
goes higher, the resultant stream is useless and packets needs to be
dropped, eventually that results in Transport Stream discontinuities.

Currently we already have a latency issue, based on the loud cries from
some people.

Thanks,
Manu

  reply	other threads:[~2006-08-31 13:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-30  6:23 [RFC] Simple userspace interface for PCI drivers Greg KH
2006-08-30 10:09 ` Thomas Gleixner
2006-08-30 14:34 ` Matt Porter
2006-08-30 16:25   ` Thomas Gleixner
2006-08-30 17:55   ` Greg KH
2006-08-30 20:32     ` Foli Ayivoh
2006-08-30 21:01     ` Matthias Schniedermeyer
2006-08-30 21:25       ` linux-os (Dick Johnson)
2006-08-30 22:08         ` Greg KH
2006-09-01  1:36     ` Brice Goglin
2006-09-01  3:22       ` Greg KH
2006-09-01  3:37         ` Brice Goglin
2006-09-01  4:27           ` Greg KH
2006-08-31 13:49   ` Andi Kleen
2006-09-01 18:16     ` Greg KH
2006-08-30 17:07 ` Manu Abraham
2006-08-30 17:52   ` Greg KH
2006-08-30 22:50     ` Manu Abraham
2006-08-31  0:17       ` Greg KH
2006-08-31 13:24         ` Manu Abraham [this message]
2006-08-31 22:42           ` Greg KH
2006-08-31  7:40 ` Andrew Morton
2006-08-31  8:05   ` Thomas Gleixner
2006-08-31  8:30 ` Xavier Bestel
2006-08-31 20:39   ` Lee Revell
2006-08-31 20:53     ` Chris Friesen
2006-08-31 21:39       ` Greg KH
2006-08-31 20:58     ` Xavier Bestel
2006-08-31 21:12       ` Lee Revell
2006-08-31 21:18         ` Xavier Bestel
2006-08-31 21:33           ` Manu Abraham
2006-08-31 21:40       ` Greg KH
2006-09-01 21:17 ` Pavel Machek
2006-09-03  8:34   ` Thomas Gleixner
2006-09-12 19:47 ` Sam Ravnborg
2006-09-14  5:57   ` Greg KH

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=44F6E30E.7010501@gmail.com \
    --to=abraham.manu@gmail.com \
    --cc=adq_dvb@lidskialf.net \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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