Drobe :: The archives
About Drobe | Contact | RSS | Twitter | Tech docs | Downloads | BBC Micro

Reply to thread

A thread can only be run on one core at one time. For an application to run on more than one core simultaneously, it must be multi threaded.

Killermike has suggested giving each application its own OS context, and I have pointed out that this is a technique used in Unix systems (back in the mainframe era). It would require some rewriting of the OS and extension modules, but would it really need to be so extensive?

Rjek has rightly pointed out that a switch statement with a long list of case statements is less efficient than a jump table for handling the Wimp_Poll reason codes, but I have already agreed that any saving would be insignificant in itself.

The Wimp_Poll idea was to allow applications to respond to more than one event at a time, in a multiprocessor system. Wimp_Poll itself would become redundant because the OS would never return from it. Instead, it would call the event handlers in the jump table. I realise that you'd lose compatibility, but I don't think it would require an extensive rewrite of application code because the only effect is to change the way you get to an event handler. The advantage, in a multiprocessor system would be that an application could carry out background tasks, (responding to Null events) while simultaneously doing, say, a window redraw and, say, a task to task data transfer. Of course, if you go down that route, you might as well make it possible to register unique instances of handlers for different objects.

Having said all that, I have also suggested that you could take advantage of multi-cores by starting a new task to handle background activities (such a rasterising a print, or saving a file to memory) and that Simtec's Hydra software should be re-examined. My intention is only to offer suggestions for porting RO to new hardware with limited redesign resources, and if my understanding of processors is stuck back in the main frame era, then modern processors should be more than capable of handling those suggestions.

 is a RISC OS UserViking on 28/5/09 10:13PM
[ Reply | Permalink | Report ]

Please login before posting a comment. Use the form on the right to do so or create a free account.

Search the archives

Today's featured article

  • Cooling a RiscPC
    Like, chill out, man
     4 comments, latest by Clades on 10/8/05 8:26AM. Published: 27 Jul 2005

  • Random article

  • Archive booklets review part one
    MessengerPro, VirtualRPC, simple networking and programming guides
     20 comments, latest by jlavallin on 19/12/05 3:28PM. Published: 12 Dec 2005

  • Useful links

    News and media:

    Top developers:
    RISCOS LtdRISC OS OpenMW SoftwareR-CompAdvantage SixVirtualAcorn

    CJE MicrosAPDLCastlea4X-AmpleLiquid SiliconWebmonster


    RISCOS.org.ukRISCOS.orgRISCOS.infoFilebaseChris Why's Acorn/RISC OS collectionNetSurf

    Non-RISC OS:
    The RegisterThe InquirerApple InsiderBBC NewsSky NewsGoogle Newsxkcddiodesign

    © 1999-2009 The Drobe Team. Some rights reserved, click here for more information
    Powered by MiniDrobeCMS, based on J4U | Statistics
    "Thanks for leaving out a significant part of my statement. Is that the standard of journalism we can expect from Drobe?"
    Page generated in 0.073 seconds.