From: Greg KH <greg@kroah.com>
To: Manu Abraham <abraham.manu@gmail.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 15:42:48 -0700 [thread overview]
Message-ID: <20060831224248.GA13990@kroah.com> (raw)
In-Reply-To: <44F6E30E.7010501@gmail.com>
On Thu, Aug 31, 2006 at 05:24:30PM +0400, Manu Abraham wrote:
> 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.
Sure, when you are pushing your hardware to the maximum, you should
expect issues like this. I agree we should do as best as we can for
things like this, but when you over-subscribe your PCI bus by doing
something like this, I really recommend just buying some hardware that
will work better for you (separate PCI busses, etc. The hardware is out
there to do this properly.)
> What i have seen is that when the bus gets saturated, the CPU usage
> shoots of rather abnormally.
As is to be expected.
> When the latency goes higher, the resultant stream is useless and
> packets needs to be dropped, eventually that results in Transport
> Stream discontinuities.
Sure, that's understandable.
> Currently we already have a latency issue, based on the loud cries
> from some people.
Trying to do things the hardware is not ment to do, should not result in
cries from users :)
thanks,
greg k-h
next prev parent reply other threads:[~2006-08-31 22:43 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
2006-08-31 22:42 ` Greg KH [this message]
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=20060831224248.GA13990@kroah.com \
--to=greg@kroah.com \
--cc=abraham.manu@gmail.com \
--cc=adq_dvb@lidskialf.net \
--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