From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: linux kernel <linuxk3rnel@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mips@linux-mips.org
Subject: Re: Feasibility study: Linux on core 0, using other cores as worker cores. Octeon II
Date: Tue, 19 May 2009 17:16:54 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.1.10.0905191710460.7037@ftp.linux-mips.org> (raw)
In-Reply-To: <29f1ba300905190458y44c8aadeuc8ff914e09105a09@mail.gmail.com>
On Tue, 19 May 2009, linux kernel wrote:
> This might seem as an unusal feasibility question, but I would like to
> discuss this here at LKML to hear you views on this matter.
> The idea would be to build a IBM cell blade lookalike architecture,
> using full blown linux on core 0, using the other cores as worker
> threads.
> Possible target CPUs are Octeon II with 32 cores or more.
>
> The main goal for this would be to reduce interrupt latency for worker
> cores, having them run possibly bare-bone with an IPC method between
> core 0 and worker cores. probably DMA and HW IRQs.
>
> Is there an existing system design in the kernel already that I can
> expand/use ? Perhaps expanding/porting the cell blade IPC method.
> What would you guys think would be the most efficient approach(and
> perhaps would be acceptable to the LK maintainers for merging at a
> later stage :) ) ?
I'm not sure if there is a ready to use implementation available
anywhere, but what you've described is one of the proposed use models for
the MIPS 34K core. Of course the method of communication would differ.
You may want to search the Internet to see if you can find anything
relevant. Since the Octeon is a MIPS architecture implementation too I've
cc-ed the linux-mips list, where you might be able to get additional
responses; also about the 34K.
Maciej
next prev parent reply other threads:[~2009-05-19 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 11:58 linux kernel
2009-05-19 16:16 ` Maciej W. Rozycki [this message]
2009-05-19 16:43 ` David Daney
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=alpine.LFD.1.10.0905191710460.7037@ftp.linux-mips.org \
--to=macro@linux-mips.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linuxk3rnel@gmail.com \
/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
Powered by JetHome