linux-kernel - Feasibility study: Linux on core 0, using other cores as worker cores. Octeon II

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 19 May 2009 13:58:41 +0200
From:	linux kernel <linuxk3rnel@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Feasibility study: Linux on core 0, using other cores as worker 
	cores. Octeon II

Hi,

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 :) )  ?

Best Regards,
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/