Author
Topic: Toro Kernel (Read 4984 times)

Hi folks!i mentioned that in the past few months ne toro kernel is again in development. the creator of toro (Matias E. Vara) is doing a great job to update the kernel !!!the tcp stack is updated and working ... i have the "briliant" idea to create a fpc cloud infrastruture for web apps based on toro/fpc.the main concepts are:1/ monoblock app running in vm based on toro ( the base idea of toro)2/ simple single user non concurent but async flie system ( todo - help needed on that)3/ communication with intranet DB (mysql, postgres etc) and cache servers (redis, memcache ...) .. native (no dll or .so ) clients implementations of the protocols is to be done - help needed... or maybe a thin tcp/http warpper based on json for communication with the servers?4/ serving web requests on the extranet with a very fast (bare metal) http server 5/ running apps in vm deployed by platform like openskack 6/ no code injection possible due to the monoblock concept of toro - app is compiled and part of the kernel - one vm is runing a single kernel with the app embeded7/ no interpreded languages - no risk 8/ minimal overhead no additional drivers except for ethernet and disk

Hi everyone, I have just moved the toro repo to github: https://github.com/MatiasVara/torokernel. I am also trying to organize the TODO work by using project and issue sections. Fell free to go through!

Hi everyone, I would like to share my last work related with Toro. Toro is now able to run as KVM guest. This is still experimental but I think work is going well. To show this, I deployed ToroHello example in a VM which anyone can see by connecting a VNC client to 51.15.142.20:5900. This is still a very simple example however it shows how easily a freepascal application can be deployed in the cloud. This application is quite fast since there is no OS, only TORO.

great new matias!!! on my side im advancing on the rest api backend ... soon we can test to compile the server under toro.. do you have an idea im is possible to deploy toro as a digital ocean droplet... cannot find any info about the vm they use... kvm docker or other... anyway toro is great

Toro has very particular architecture in which certain applications are improved but other gets no too much benefices. Toro is good when an application can be split in pipelines. In that case, you can run every pipeline in a different core and then dedicate all the resources needed by core. This reduces a lot the overhead due to shared resources. In addition, switch context are very light.

Hi everyone, I would like to share my last work related with Toro. Toro is now able to run as KVM guest. This is still experimental but I think work is going well. To show this, I deployed ToroHello example in a VM which anyone can see by connecting a VNC client to 51.15.142.20:5900. This is still a very simple example however it shows how easily a freepascal application can be deployed in the cloud. This application is quite fast since there is no OS, only TORO.

Regards, Matias.

If you like I Worked a little In ToroKernel I tried to put the KernelModuled in a Package, but I didn't without success (maybe you Could help)But I managed to get My Writepascal-demo running.

that crashed because Copy() is no PtrUintSo i exported the PrintString Procedure and enabled PutC to handle the backspace-Character First test looked promising, But then the next drawback:When you write something like 'abc'+s (:ansistring) you get an error (Wrong parameter in Concat)When you do copy(s {:ansistring = '123456'} ,1,7) The output went nuts (lot of stupid characters).When you do copy('123456' ,1,7) get an error (Wrong parameter ) Shortstring to ansistring..That went on ...Before final version I tied

Error Char to ansistring wrong parameter. the final version With PutC exportet worked at last.

Please rename the procedure (or overload it If you like) WriteConsole has no indication that it needs Format-Parameters a name like WriteConsoleFmt would indicate that, like the MessageFmt Function, Even in C printf means print formatted on the contrary to write that prints unformatted.