From: Jeff Garzik <jgarzik@pobox.com>
To: Andre Bonin <kernel@bonin.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI coprocessors
Date: Wed, 15 Sep 2004 12:01:25 -0400 [thread overview]
Message-ID: <41486755.3070207@pobox.com> (raw)
In-Reply-To: <41483BD3.4030405@bonin.ca>
Andre Bonin wrote:
> 1) Is their support for having two different 'machine types' within one
> kernel? that is for example, certain executables for intel would get run
> on an intel processor, and others would get run on processor with type
> XXXX.
>
> I heard once someone put native "java" .class support within the kernel
> (it would call the jvm run time if i remember). I could maby do this
> with my own set of libraries and driver. But differentiating between
> the types of executable might be hard.
>
> 2) Is their kernel support for PCI coprocessors for thread allocation
> etc. I couldn't find any but i can try looking through the code again.
You can mix and match processor types all you want... just treat them
as completely asynchronous and independent entities.
I have long dreamed of being able to add a PCI card to my x86 system, a
PCI card containing a processor (of any type), RAM, and an ethernet
interface. I would use this for routing, or iSCSI, or network offload...
Jeff
next prev parent reply other threads:[~2004-09-15 16:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 12:55 PCI coprocessors Andre Bonin
2004-09-15 12:30 ` Alan Cox
2004-09-15 13:44 ` Matti Aarnio
2004-09-15 13:45 ` Richard B. Johnson
2004-09-15 14:55 ` Tomasz Rola
2004-09-15 15:15 ` Andre Bonin
2004-09-15 16:49 ` Tonnerre
2004-09-16 0:12 ` Tomasz Rola
2004-09-15 16:01 ` Jeff Garzik [this message]
2004-09-15 22:39 ` Tonnerre
2004-09-17 10:16 ` Andre Tomt
2004-09-17 16:19 ` Tony Lee
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=41486755.3070207@pobox.com \
--to=jgarzik@pobox.com \
--cc=kernel@bonin.ca \
--cc=linux-kernel@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 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.