From: Bill Davidsen <davidsen@tmr.com>
To: Benny Amorsen <benny+usenet@amorsen.dk>
Cc: linux-smp@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: smp and irq conflict
Date: Wed, 14 Feb 2007 11:45:53 -0500 [thread overview]
Message-ID: <45D33CC1.7040709@tmr.com> (raw)
In-Reply-To: <m3zm7suc5o.fsf@ursa.amorsen.dk>
Benny Amorsen wrote:
>>>>>> "BD" == Bill Davidsen <davidsen@tmr.com> writes:
>>>>>>
>
> BD> You may be able to move one board to another slot, but looking at
> BD> the bandwidth I suspect you may need a server motherboard with
> BD> multiple busses, preferably running at 66MHz 64bit. I don't think
> BD> this is a interrupt problem, but you can just try capture on two
> BD> channels which share an interrupt, like bttv0 and bttv7 to verify
> BD> that.
>
> 66MHz 64bit isn't much fun when the capture cards are 33MHz 32bit.
>
>
It doesn't help the video to bus, but multiple busses to give a bus per
card would help, and assuming the data are being saved to disk using a
decent disk controller which can use the additional bandwidth, at least
some conflict is avoided or reduced.
This is really a case of using general hardware to the utmost, I suspect
more m/b bandwidth will be needed somewhere.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2007-02-14 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 17:46 smp and irq conflict Lapo TIN
2007-02-02 4:32 ` Andrew Morton
2007-02-02 5:22 ` Len Brown
2007-02-02 14:52 ` Bill Davidsen
2007-02-05 10:33 ` Benny Amorsen
2007-02-14 16:45 ` Bill Davidsen [this message]
[not found] <fa.bd33YMixT9/jJwHfbD/DebGgVXs@ifi.uio.no>
2007-02-01 23:29 ` Robert Hancock
2007-02-02 0:04 ` Lapo TIN
2007-02-02 0:59 ` Robert Hancock
2007-02-02 11:08 ` Erik Mouw
2007-02-14 17:59 ` Manu Abraham
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=45D33CC1.7040709@tmr.com \
--to=davidsen@tmr.com \
--cc=benny+usenet@amorsen.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-smp@vger.kernel.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