Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: minforth Newsgroups: comp.lang.forth Subject: Re: multitasking vs multiple interpreters Date: Tue, 29 Jul 2025 06:03:56 +0200 Lines: 15 Message-ID: References: <871pq0uppw.fsf@nightsong.com> <87wm7ru0y4.fsf@nightsong.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net iW/910F7v/WGywIn7gTdQAcEZPG8q20Y0D+qp1qeHWDVbdSbIJ Cancel-Lock: sha1:OJY3R15CDMAYKLeYj96UpNeQzkY= sha256:ZNkSA4x5hvm2wbLXoVkZC+Kv2fjJ74QhVAtELXLEfdM= User-Agent: Mozilla Thunderbird In-Reply-To: <87wm7ru0y4.fsf@nightsong.com> Xref: csiph.com comp.lang.forth:134103 Am 29.07.2025 um 05:32 schrieb Paul Rubin: > albert@spenarnc.xs4all.nl writes: >> The other situation is that you take advantage of multiple cores >> to speed up the calculation. There you use the fork system call. > > The idea here is to multitask on an MCU with around 2kB of memory, so no > OS. Just a few tasks to monitor a pushbutton, control a LED, and some > similar things. The scheduler will require a base clock interrrupt, say every 10 millisecs. Other interrupts can fill a request queue which is handled by the scheduler. Details are VERY hardware specific. You may be interested in: https://codeberg.org/clausecker/mecrisp-stellaris